Meta-Wiki - User contributions [en]

Updating the ecosystem of Wikimedia organizations/Future Affiliate Landscape

2026-03-09T02:36:34Z

Bryandamon: Fixed paper name.

== Proposal - Future Affiliate Landscape ==
{{Draft}}
{{CSS image crop
|Image = Bee_bums_(245215927).jpg
|bSize = 900
|cWidth = 900
|cHeight = 300
|oTop = 240
|oLeft = 0
|Location = center
|Description =
|Link =
|Alt = Bees in a beehive
|Page =
|magnify-link =
}}
__NOTOC__
This is a proposal from [[Updating the ecosystem of Wikimedia organizations|the pilot on the ecosystem of Wikimedia organizations]]. Following the publication of the paper [[Towards_a_Healthy_Ecosystem_of_Wikimedia_Organizations|Towards a Healthy Ecosystem of Wikimedia Organizations]], a [[Updating_the_ecosystem_of_Wikimedia_organizations#Focus_group|focus group]] was formed in December 2025 to come up with a proposal for next steps. This proposal is the outcome of this work.

The purpose of the proposal is to provide a basis for future conversations around movement organizations and advance the process towards action and implementation of needed changes. The main goal is to achieve clarity regarding the structure of movement organizations, especially the purpose, role, rights, and expectations related to each organization type, as well as how different organization types are connected to each other.

===Affiliate definition===
A Wikimedia affiliate is an organization or organized group of people with its main purpose to work towards the Wikimedia vision, supporting people and institutions to contribute to the sum of all human knowledge in their context and locality.

===Affiliate purpose - contextual and local===
*'''Adhere to vision.''' Deliver the Wikimedia vision in context and at the local level. Make it tangible and culturally relevant.
*'''Outreach.''' Through their unique position, affiliates help the movement to reach more people and organizations. Connect to them and connect them to Wikimedia vision, expanding the movement. Be present in their context and locality.
*'''Support.''' Provide contextual and local support to people connected to Wikimedia. Create opportunities for participation and meaningful contribution.

===Affiliate principles - equity, subsidiarity, and support===
*'''People-centeredness.''' Focus on people who empower Wikimedia. Meet their needs in context. Reduce barriers to contribution and nurture community health.
*'''Equity through contextualization.''' Local and contextual approach helps to provide support and opportunities for people to participate at appropriate levels regarding their capacity and context. Equity considers that some people and communities start with a disadvantage, needing focus support in overcoming challenges.
*'''Subsidiarity in action.''' Affiliates are in a unique position to connect global and local levels in the movement. Affiliates increase the agency and participation of individuals, bringing decisions closer to people, and increasing the capacity for self-management.
*'''Anchoring support system.''' Affiliates are the guiding mechanism and support system for content-creating communities, creating a platform for community members to focus on quality contributions.

===Affiliate recognition===
*'''Recognition.''' Suggested criteria:
** Alignment with Wikimedia vision. The main goal of the group or organization is well aligned with Wikimedia vision and common movement goals.
** Clarity of scope. Clearly defined reach in terms of communities, geographies and themes supported. Clear outline of activity areas and proposed services.
** Clear reason to be affiliated. It needs to be clear why and how the affiliation status will improve the quality and impact of the group.
*'''Derecognition.''' Affiliates need to be derecognized in occurrence of significant break of the affiliate agreement, deliberate malfeasance, not abiding by the conduct commitment, and continued inactivity.

===Affiliate focus areas===
*'''Enable impactful quality content.''' Support the communities to develop quality contextual content and maintain information integrity on challenging topics. Partner with expert organizations to be part of quality content creation.
*'''Organize.''' Organize content-creating communities. Recruit and welcome new members, promote the activities, provide governance support and structure for communities to thrive.
*'''Resource communities.''' Facilitate work on the content and create access to resources for content-creating community members. Resources include reference materials, capacity and leadership development, support for community health, tools and widgets, and financial means (incl fundraising).
*'''Foster the environment.''' Increase awareness about Wikimedia vision and ways of working by using common narratives in context. Advocate locally and regionally for better conditions for our projects and communities to flourish.
*'''Manage partnerships.''' Connect with organizations and governments. Leverage brand awareness and institutional legitimacy in specific context and on a local level. Facilitate delivery on Wikimedia vision through these connections.
*'''Connect the movement.''' Connect people within, across, and beyond the Wikimedia movement. Create and maintain peer learning spaces. Identify trends, movements, and influences around Wikimedia to take collective action. Expectation for established affiliates to support emerging ones.

===Affiliate accountability===
For each and every affiliate, there is an expectation to have a:
*'''Common goal.''' The primary goal of any Wikimedia affiliate is to advance the common Wikimedia vision and agreed upon common movement goals. This is the main difference between a Wikimedia affiliate and any other, even allied organization. Align affiliate purpose, focus, accountability, and funding to common movement goals
*'''Conduct commitment.''' Affiliates have a foundational role in shaping the culture of the movement. Every affiliate needs to have a code of ethics or abide by Universal Code of Conduct regulating relationships between members, with the community, and wider movement. As a good governance practice, a conflict of interest policy needs to be in place
*'''Clear communication.''' Documentation, reporting, and sharing of stories makes the affiliate role visible and understandable. It is the foundation for sharing best practices and peer learning across the movement.
*'''Clear governance.''' Affiliates need to establish clarity regarding their basic governance model and how people can be involved in the affiliate overall and in its decision-making in particular.
*'''Impact assessment.''' Every affiliate needs to have a clear impact assessment model to create clarity on how their work contributes to achieving common movement goals, share the lessons learned for future improvement, and create opportunities for collective action around global trends. The level of reporting needs to correspond to the level of capacity of the affiliate and complexity of its work.

For established affiliates there is an expectation for:
*'''Peer mentorship.''' Experienced affiliates are best positioned to support young affiliates and emerging communities planning to organize. Peer mentorship needs to be their explicit commitment to make this a reality across the movement.
*'''Fiscal sponsorship.''' There needs to be a sustainable model for fiscal sponsorships, especially for emerging groups and groups that cannot have a formal structure due to safety concerns.

===Advantages of affiliating===
* '''Trademark use.''' Every affiliate has access to the use of the Wikimedia trademarks to advance the mission and increase awareness about Wikimedia in legally appropriate ways.
* '''Access to structured support.''' Affiliates have access to receive structured support to increase their capacity or overcome challenges. Support is provided by peer networks and the Wikimedia Foundation.
* '''Access to funds.''' Affiliates access Wikimedia grants. The funding will depend on the demonstrated capacity of the affiliate, its overall health and track record, and its growth trajectory. Every affiliate receiving funds has a responsibility to publicly report on the use of funds.
* '''Fundraising.''' Affiliates may fundraise. Every affiliate taking part in fundraising has a responsibility to coordinate its activities on the field with other organizations to avoid duplication of efforts.

===Affiliate growth===
* '''Affiliate health review.''' There needs to be a systemic approach to assess the health of affiliates. This can prompt support to affiliates as well as forecast their growth trajectories and future needs.
** Build on impact assessment and reports from affiliates themselves.
** Highlight the impact of affiliates and its connection to common goals of the movement.
** Find ways to meaningfully assess the actual health of affiliates, considering its capacity, governance practices, people management, and finances.
** Use the review to define areas of support and peer connections to improve the overall health of affiliates.

*'''Affiliate tiers.''' It makes sense to have different tiers of affiliates based on their capacity to deliver impact to achieve Wikimedia vision.

{| class="wikitable"
|- style="font-weight:bold; text-align:center; background-color:#EFEFEF;"
! Category
! Light
! Versatile
! Established
|-
| style="text-align:center; background-color:#EFEFEF;" | Formalization
| Not formalized.
| Formalized processes.
| Formalized organizations.
|-
| style="text-align:center; background-color:#EFEFEF;" | Delivery
| Project or a few
| Different programs. 2-3 focus areas.
| Wide range of programs. 4+ focus areas.
|-
| style="text-align:center; background-color:#EFEFEF;" | Partnerships
| Project related partnerships.
| 1-2 sustained partnerships.
| A number of sustained partnerships
|-
| style="text-align:center; background-color:#EFEFEF;" | Assessment
| Basic impact assessment
| Impact assessment system on focus areas
| Established impact assessment.
|-
| style="text-align:center; background-color:#EFEFEF;" | Contribution
| No expectations
| Participate in peer learning
| Drive peer mentorship and provide fiscal and HR sponsorship
|-
| style="text-align:center; background-color:#EFEFEF;" | Funding / staff
| No or temporary funding / staff
| Mostly project focused funding and staff
| Operational and programmatic funding, may fundraise, have staff
|}

* '''Flexibility.''' Suggestion for the tiered system should not to be one-directional and not only to be aimed towards growth.
** Affiliates need to be able to move between tiers based on changing contextual and local needs and expectations or circumstances.
** Any need for re-registration of affiliates that are legal entities needs to be avoided.

===Hubs and partner organizations===
* '''Hubs.''' Hubs are a coordination and service structure, a framework for collaboration between affiliates, communities, and individuals.
** Hubs are created to reach overarching goals that are difficult to achieve on the scale of affiliates, communities or individuals.
** Hubs are expected to provide support to communities and affiliates in their region or thematic area of work, where a clear need has been identified and their establishment has been endorsed by communities serviced.
** No duplication. Hubs need to support a number of communities and affiliates within its scope. There should not be regional or thematic overlap between hubs. In case of potential overlap, coordination needs to happen between hubs.
** Hubs are expected to have access to Wikimedia grants. The funding should not duplicate, rather complement or support stakeholder activities in their area of service or effect.
** Hubs are not expected to be affiliates themselves, but a different layer of organizing the movement.
** Hubs are not expected to be registered entities. However, hubs can be organizations if it benefits accomplishment of their goals.
** Affiliate accountability criteria would also apply to the hubs.

*'''Partner organizations.''' Allies and partners in achieving Wikimedia vision need to be involved and recognized in a way for stronger impact, especially around public knowledge.
** Have a formalized status of partner organizations or movement allies to create a clear connection with Wikimedia for organizations whose work aligns with Wikimedia vision.
** Access to Wikimedia trademarks on a program or project basis can be granted to increase awareness in agreed upon ways.
** Access to Wikimedia grants is dependent on the impact of Wikimedia-aligned activities.
** It does not make sense to have them affiliated, as their mission probably aligns with Wikimedia's, but it is not solely focused on the Wikimedia projects.
** Affiliate accountability criteria would also apply to partner organizations.

===Affiliate funding===
* '''Clarity.''' Ensure that there is clarity regarding the requirements of funding from entry level affiliates to established organizations.
* '''Impact.''' Funding needs to be clearly tied to potential and demonstrated capacity and impact level rather than the size of the affiliate.
* '''Innovation.''' Funding needs to accommodate flexibility, not only sustainability. There is potential for organizations to experiment and innovate. After proof of concept the innovation can be adopted at scale by other organizations.
* '''Stability.''' Multi-year funding should not be available only for established organizations and bigger budgets. To create core stability for flexibility of affiliates, multi-year support can also be provided to smaller organizations with smaller budgets with a good track record, clear impact model and development path.
* '''Collaboration.''' There need to be financial incentives for Wikimedia grant recipients to work together on common goals towards collective impact. Peer connections can be a responsibility included in the grant program, increasing the funds available.

[[Category:Ecosystem of Movement Organizations]]

Talk:North American Wikimedians/Hub founding

2025-05-09T18:15:16Z

Bryandamon: /* Would your group sign on? How should the agreement text be revised? */ Added MWStake support.

{{NAhub founding}}
== Would your group sign on? How should the agreement text be revised? ==

* [[Wikimedia DC]] will sign on. Please do edit the content or phrasing of the agreement; let's get it right and get 10 groups to sign. -- [[User:Econterms|econterms]] <small>([[User_talk:Econterms|talk]])</small> 15:45, 8 June 2024 (UTC)
* [https://en.wikipedia.org/wiki/Wikipedia:Meetup Philadelphia WikiSalon] supports the initiative for a North American Hub. -- [[User:Dorevabelfiore|Dorevabelfiore]] ([[User talk:Dorevabelfiore|talk]]) 18:49, 8 June 2024 (UTC)
* [[Wikimedia New York City|Wikimedia NYC]] has support of the concept, and we will bring this proposed agreement to our board.--[[User:Pharos|Pharos]] ([[User talk:Pharos|talk]]) 00:23, 30 July 2024 (UTC)
* On behalf of the [[Wikimedians of Los Angeles|Wikimedians of Los Angeles User Group]], we are glad to lend our full support to this initiative. --[[User:Sky Harbor|<font color="#0066ff" ><b>Sky Harbor</b></font>]] <sup>([[User talk:Sky Harbor|<font color="#0066ff" ><b>talk</b></font>]])</sup> 23:46, 30 October 2024 (UTC)
* The [[North Carolina Wikipedians|North Carolina Wikipedians User Group]] supports the North American Hub. -- [[User:Sodapopinski7|Sodapopinski7]] ([[User talk:Sodapopinski7|talk]]) 20:11:29, 10 November 2024 (UTC)
*The [[Wikimedians of Colorado User Group]] fully supports the North American Hub. -- [[User:Buaidh|<span style="color:white;background-color:#770022;font-weight:bold;"> Buaidh </span>]]<span style="font-size:75%;vertical-align:middle;"> [[w:User talk:Buaidh|talk]] [[Special:EmailUser/Buaidh|e-mail]]</span> 01:11, 3 December 2024 (UTC)
*The [[Bay Area Wikipedians User Group]] supports the North American Hub. -- [[User:E_mln_e|E_mln_e]] ([[User talk:E_mln_e|talk]]) 11:01, 4 December 2024 (UTC)
*[[Wikimedians of Chicago User Group]] will join the North American Hub [[User:Luiysia|Luiysia]] ([[User talk:Luiysia|talk]]) 20:31, 14 December 2024 (UTC)
* [[Wikimedia Canada]] supports the initiative for a North American Hub. -- [[User:Louis Germain (WMCA)|Louis Germain (WMCA)]] ([[User talk:Louis Germain (WMCA)|talk]]) 22:00, 24 February 2024 (UTC)
* [[AfroCROWD]] supports the initiative for a North American Hub. [[User:Shanluan|Shanluan]] ([[User talk:Shanluan|talk]]) 06:50, 25 February 2025 (UTC)
*[[Cascadia Wikimedians]] supports the initiative for a North American Hub. [[User:Peaceray|Peaceray]] ([[User talk:Peaceray|talk]]) 22:15, 24 February 2025 (UTC)
* [[mw:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]] supports the initiative for a North American Hub. -- [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 18:15, 9 May 2025 (UTC)

=== Clarify supportive purpose ===

'''Change''':
: ''We will host events, activities, or services open to North American Wikimedians regularly and we can say such events are held on behalf of in concert with of the North American hub''

to read
: ''We will host events, activities, or services open to North American Wikimedians, and support one another's events.''

* +1 as proposer. –[[User:Sj|SJ]]<small> [[User Talk:Sj|<font style="color:#f90;">talk</font>]] </small> 21:52, 29 July 2024 (UTC)
** Adopted with tweaks; see my general reply below.

=== Reduce exclusivity ===
The hub should support all initiatives to improve Wikimedia across the region. We cannot become a secondary layer of approval for affiliate status. Voting should be kept to a minimum, and replaced by structural defaults where possible, or by simple RfCs as already understood on Meta.

'''Change''':
: ''By majority vote of existing member groups, new groups can join the hub. A group can leave whenever it decides to.''
to read
: ''Any Wikimedia affiliates based in North America can join the hub by signing on to this agreement. A group can leave whenever it decides to.''
** Adopted, with minimal rephrasing. -- [[User:Econterms|econterms]] <small>([[User_talk:Econterms|talk]])</small> 06:10, 8 August 2024 (UTC)

'''Change''':
: ''By majority vote of existing member groups, project may be approved or declined as "North American Wikimedians" (hub)
to read
: ''Any project or event by members of the hub can be announced on our [[NARWHAL/projects|projects]] page.''

'''Add''':
: ''Other groups (including partner orgs that are not affiliates) may be proposed for inclusion in the Hub, or for removal from the Hub, by an RfC on the [[Talk:NARWHAL|talk page]].''

* +1 as proposer. –[[User:Sj|SJ]]<small> [[User Talk:Sj|<font style="color:#f90;">talk</font>]] </small> 21:52, 29 July 2024 (UTC)
**

; Comments
:: [[User:Sj|SJ]]:
:: I'll happily fold some of this in. I agree with minimizing voting, and thought I had. And I certainly agree that this hub mustn't "become a secondary layer of approval for affiliate status." -- nobody wants that, to my knowledge.

:: However, regarding the first change, I don't want to accept the suggested rephrasing exactly. I didn't want to use that proposed criterion "based in North America", and preferred "offering services to North Americans". E.g. LGBT+ or Francophone or Wiksource user groups might be based elsewhere, but active enough in North America to join.
::: Updated the last suggestion, so it can include groups that are not specific to N.America. Those shouldn't be automatically included, but groups within the region should be -- that's what it says on the tin. –[[User:Sj|SJ]]<small> [[User Talk:Sj|<font style="color:#f90;">talk</font>]] </small> 00:12, 30 July 2024 (UTC)
:: I felt it was important to say not only that a group wants to join the hub, and signs on to this agreement, but that the others accept and welcome it. There is some idea out there called collecting hats? collecting roles or powers or items for the vita? or joining everything? and I think we don't want to give membershp/credit/votes to inactive or irrelevant members even if they would sign. I'll reflect further. -- [[User:Econterms|econterms]] <small>([[User_talk:Econterms|talk]])</small> 23:48, 29 July 2024 (UTC)
::: I don't think hubs should be social clubs. They should by default support all efforts in their region or focus, especially those without other support networks. There's nothing to 'collect' -- every org should be part of a hub if they want to be. (possibly not more than one, in which case you choose which you join; that's a norm we should set across all the hubs. But none excluded simply for lack of popularity.) –[[User:Sj|SJ]]<small> [[User Talk:Sj|<font style="color:#f90;">talk</font>]] </small> 00:12, 30 July 2024 (UTC)
::: {{ping|econterms}} would love some iteration and broader discussion before Wikimania :) –[[User:Sj|SJ]]<small> [[User Talk:Sj|<font style="color:#f90;">talk</font>]] </small> 22:23, 30 July 2024 (UTC)
:::: {{ping|Sj}} I'm slow! But I halfway adopted these improvements. Thank you for thinking it through. I feel that some backstop of formal decisionmaking is necessary in cases of true disagreement or bad faith. But this is not central, so I scooted that bit down into a subsection and made plain that voting would not be a regularly scheduled recurring matter; possibly it's needed only for exceptional cases. I'm not sure you will find it to be better. It's longer. But by separating section that away we can use your simpler friendlier general and direct phrasings in the top section. -- [[User:Econterms|econterms]] <small>([[User_talk:Econterms|talk]])</small> 06:10, 8 August 2024 (UTC)

== Suggestion to avoid control of Hub by dominant nation ==

It has been suggested that governance procedures be adapted to make sure that the US chapters and user groups could not control the agenda entirely. We could tweak the proposed procedures to reduce the chance of this danger, e.g. by making a rule that all proposals for projects or new members have international support. If we go this direction let's find some rule that is easy and feasible. -- 04:14, 15 February 2025 (UTC) [[User:Econterms|econterms]] <small>([[User_talk:Econterms|talk]])</small> 04:14, 15 February 2025 (UTC)

Wikibase/Consultants and Support Providers

2023-10-25T19:52:39Z

Bryandamon: /* Overview of providers */ Changed checks to text so sort works and table can be exported.

{{ambox|type=warning |text=This is not a page for job posts or job advertisements. If you need Wikibase help, contact the individual service provider or company personally and privately.}}

This page is intended to help you find help with your Wikibase if you need it. Inclusion of a service provider on these lists does not constitute an official endorsement by the Wikibase team.

The lists do not claim to be exhaustive. If you think you or your company should be listed on the page, you are welcome to add it yourself.

== Overview of providers ==

{| class="wikitable sortable mw-collapsible" style="width: 95%;"
|+
|-
! scope="col" |Name
! scope="col" |Location
! Wikibase operations and support
! Wikibase custom development
! Wikibase data modeling
! Wikidata consulting
|-
|{{sortkey|Digitaal Werktuig|[[#Digitaal Werktuig|Digitaal Werktuig]]}}
|{{sortkey|Netherlands, Amersfoort|Amerfoort, Netherlands}}
|
|
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|-
|{{sortkey|Inventaire|[[#Inventaire|Inventaire]]}}
|{{sortkey|France, Lyon|Lyon, France}}
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
|
|
|-
|{{sortkey|IP-Squared|[[#IP-Squared|IP-Squared]]}}
|{{sortkey|Netherlands, Amsterdam|Amsterdam, Netherlands}}
|
|
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|-
|{{sortkey|Knowledge Management Associates|[[#Knowledge Management Associates|Knowledge Management Associates]]}}
|{{sortkey|Austria, Vienna|Vienna, Austria}}
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
|-
|{{sortkey|Micelio|[[#Micelio|Micelio]]}}
|{{sortkey|Belgium, Antwerpen|Antwerpen, Belgium}}
|
|
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|-
|{{sortkey|QA Company, The|[[#The QA Company|The QA Company]]}}
|{{sortkey|France, Saint-Etienne|Saint-Etienne, France}}
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|-
|{{sortkey|Scatter|[[#Scatter|Scatter]]}}
|United States
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|-
|{{sortkey|Wiki Valley|[[#Wiki Valley|Wiki Valley]]}}
|{{sortkey|France, Paris|Paris, France}}
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
|
|
|-
| {{sortkey|Wikibase Consultancy, The|[[#The Wikibase Consultancy|The Wikibase Consultancy]]}}
| {{sortkey|Germany, Berlin|Berlin, Germany}}
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
|
|-
|{{sortkey|WikiTeq|[[#WikiTeq|WikiTeq]]}}
|{{sortkey|United States, Florida, Boca Raton|Boca Raton, Florida, United States}}
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
|
|-
|{{sortkey|WikiWorks|[[#WikiWorks|WikiWorks]]}}
|{{sortkey|United States, New Jersey, Pennington|Pennington, New Jersey, United States}}
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
| style="color:#04A884; font-weight:bold; text-align:center" | &check;
|
|}

==More details==

=== Digitaal Werktuig ===
Digitaal Werktuig helps clients to share digital information, knowledge and culture as broadly as possible. In doing so, Digital Werktuig contributes to an open society, with engaged citizens. Digitaal Werktuig advises and supports organisations, projects and initiatives on matters concerning information technology.

Digitaal Werktuig is a freelance enterprise founded by Maarten Brinkerink (Est. October 2020). Maarten Brinkerink is an expert in digital culture and information processing. He is an experienced project manager, researcher and consultant, working in the cultural heritage sector for 15 years. Next to his freelance activities, Maarten also works at the Netherlands Institute for Sound & Vision as an IT solution architect.

* Website: {{sortkey|Digitaal Werktuig|[http://www.digitaalwerktuig.nl/en Digitaal Werktuig]}}
* Email: info@digtiaalwerktuig.nl

=== Inventaire ===
Besides inventaire.io, inventaire team can setup, configure and maintain Wikibase instances. In 2019, the team worked with [https://github.com/abes-esr/poc-fne-wikibase-docker/tree/poc-fne BNF and ABES] to setup a proof of concept based on Wikibase
* Website: [https://inventaire.io Inventaire]
* Email: hello@inventaire.io

=== IP-Squared ===
IP Squared provides strategic information advice. IP Squared is specialised in projects around access to information, knowledge and culture. IP Squared works for public institutions such as (local) governments and heritage institutions. Projects by IP Squared are about legal and technological challenges around information and knowledge management, including intellectual property, data architecture, data modelling, linked open data, etc.

IP Squared is wholly owned by Maarten Zeinstra, LL.M. M.Sc.

* Website: {{sortkey|IP-Squared|[https://www.ip-squared.com/ IP-Squared]}}
* Email: info@ip-squared.com

=== Knowledge Management Associates ===
Consulting and implementation of Wikibase & Semantic MediaWiki solutions. Linking data with Wikidata.

* Website: [https://km-a.net/knowledge-wiki/ KM-A (Knowledge Management Associates)]
* Email: bernhard.krabina@km-a.net

=== Micelio ===
Micelio is involved in various implementation and research projects on using Wikidata. Most notably the Gene Wiki project where biomedical public databases are aligned with Wikidata. While Wikidata remains core, various use cases emerged where data is not eligible for inclusion in Wikidata (e.g. non-public reuse licenses or in need of a data model that is not yet implemented on Wikidata). In close collaboration with others we then explore the possibilities of deploying and reusing wikibase to allow creating a federated landscape of deployed wikibases that have Wikidata as a core. This through running Proof-of-concept studies or assisting in "Bring your own data" workshops, where participants are assisted in adding their data to a wikibase.

* Website: {{sortkey|Micelio|[http://www.micelio.be Micelio]}}
* Email: andra@micel.io

=== The QA Company ===
We are currently maintaining the Wikibase infrastructure of the European Commission at https://linkedopendata.eu. This includes setup, installation of extensions, customisation of logos, login with oAuth and more. We are also integrating data of the European Commission about countries, capitals, head of states, buildings, projects financed by the Commission and many more. The Wikibase is currently feeding different services like [https://kohesio.eu this public website]. Do not hesitate to contact us!

Our Wikibase data modelling expertise includes: deep knowledge of semantic modelling, the ability to reuse entities from Wikidata in local installations, keeping knowledge imported from Wikidata fresh, linking customer entities with Wikidata entities to profit from the efforts made by the Wikidata community.

* Website: [https://the-qa-company.com The QA Company]
* Email: info@qanswer.eu

=== Scatter ===
[[User:Harej|James Hare]] has been tinkering with custom Wikibases since 2015. Whatever the state of your data, get it fit for Wikidata, custom Wikibase, or interoperability with Wikidata. Wikidata and Wikipedia community relations. Private Wikidata query service. Registered in [https://sam.gov SAM] as a government contractor.

* Website: [https://scatter.red Scatter]
* Email: james@scatter.red

=== Wiki Valley ===

* Website: Wiki Valley ([https://en.wiki-valley.com/ en]) ([https://wiki-valley.com/ fr])
* Email: contact [[File:Meuble héraldique arobase.svg|22x22px]]wiki-valley.com

=== The Wikibase Consultancy ===

* Also known as [https://professional.wiki Professional Wiki]
* [https://professional.wiki/en/hosting/wikibase Tailored Wikibase hosting] and [https://www.pro.wiki/wikibase-hosting Wikibase cloud hosting]
* [https://www.wikibase.consulting/about-the-wikibase-team/ Developer that created Wikibase] and [https://www.wikibase.consulting/blog/ multiple Wikibase extensions]
* 240+ wikis hosted, MediaWiki development for 15+ years, 48000+ code changes
* [https://professional.wiki/en/jobs We are hiring]
* <span style="white-space: nowrap">Website: [https://wikibase.consulting The Wikibase Consultancy]</span>
** {{sortkey|Professional.Wiki|Professional.Wiki [https://professional.wiki (en]) ([https://Professional.Wiki/de de])}}
* Email: info@professional.wiki

=== WikiTeq ===
Full-service Wikibase & MediaWiki solutions, including site setup, extension development, skin design, semantic technologies, hosting, and continued support. Headed by Ike Hecht.

* Website: [https://www.wikiteq.com/ WikiTeq]
* Email: contact@wikiteq.com

=== WikiWorks ===
We are a consulting company, formed in 2009, that implements MediaWiki solutions for clients large and small. Our founder, Yaron Koren, is a veteran MediaWiki programmer who is one of the key developers of so-called "Enterprise MediaWiki". On our staff we also have other MediaWiki developers, and people with significant experience implementing MediaWiki solutions.

* Website: [https://wikiworks.com/ WikiWorks]
* Email: [mailto:info@wikiworks.com info@wikiworks.com]

==See also==
* [[mw:Professional development and consulting|Professional development and consulting for MediaWiki]], on which Wikibase is based

[[Category:Wikibase]]

Wikibase/Consultants and Support Providers

2023-10-25T19:32:35Z

Bryandamon: /* Overview of providers */ Added WikiWorks.

{{ambox|type=warning |text=This is not a page for job posts or job advertisements. If you need Wikibase help, contact the individual service provider or company personally and privately.}}

This page is intended to help you find help with your Wikibase if you need it. Inclusion of a service provider on these lists does not constitute an official endorsement by the Wikibase team.

The lists do not claim to be exhaustive. If you think you or your company should be listed on the page, you are welcome to add it yourself.

== Overview of providers ==

{| class="wikitable sortable mw-collapsible" style="width: 95%;"
|+
|-
! scope="col" |Name
! scope="col" |Location
! Wikibase operations and support
! Wikibase custom development
! Wikibase data modeling
! Wikidata consulting
|-
|{{sortkey|Digitaal Werktuig|[[#Digitaal Werktuig|Digitaal Werktuig]]}}
|{{sortkey|Netherlands, Amersfoort|Amerfoort, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Inventaire|[[#Inventaire|Inventaire]]}}
|{{sortkey|France, Lyon|Lyon, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
|{{sortkey|IP-Squared|[[#IP-Squared|IP-Squared]]}}
|{{sortkey|Netherlands, Amsterdam|Amsterdam, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Knowledge Management Associates|[[#Knowledge Management Associates|Knowledge Management Associates]]}}
|{{sortkey|Austria, Vienna|Vienna, Austria}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|
|-
|{{sortkey|Micelio|[[#Micelio|Micelio]]}}
|{{sortkey|Belgium, Antwerpen|Antwerpen, Belgium}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|QA Company, The|[[#The QA Company|The QA Company]]}}
|{{sortkey|France, Saint-Etienne|Saint-Etienne, France}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Scatter|[[#Scatter|Scatter]]}}
|United States
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Wiki Valley|[[#Wiki Valley|Wiki Valley]]}}
|{{sortkey|France, Paris|Paris, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
| {{sortkey|Wikibase Consultancy, The|[[#The Wikibase Consultancy|The Wikibase Consultancy]]}}
| {{sortkey|Germany, Berlin|Berlin, Germany}}
| [[File:Yes check.svg|15px|link=]]
| [[File:Yes check.svg|15px|link=]]
|
|
|-
|{{sortkey|WikiTeq|[[#WikiTeq|WikiTeq]]}}
|{{sortkey|United States, Florida, Boca Raton|Boca Raton, Florida, United States}}
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|
|
|-
|{{sortkey|WikiWorks|[[#WikiWorks|WikiWorks]]}}
|{{sortkey|United States, New Jersey, Pennington|Pennington, New Jersey, United States}}
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|
|}

==More details==

=== Digitaal Werktuig ===
Digitaal Werktuig helps clients to share digital information, knowledge and culture as broadly as possible. In doing so, Digital Werktuig contributes to an open society, with engaged citizens. Digitaal Werktuig advises and supports organisations, projects and initiatives on matters concerning information technology.

Digitaal Werktuig is a freelance enterprise founded by Maarten Brinkerink (Est. October 2020). Maarten Brinkerink is an expert in digital culture and information processing. He is an experienced project manager, researcher and consultant, working in the cultural heritage sector for 15 years. Next to his freelance activities, Maarten also works at the Netherlands Institute for Sound & Vision as an IT solution architect.

* Website: {{sortkey|Digitaal Werktuig|[http://www.digitaalwerktuig.nl/en Digitaal Werktuig]}}
* Email: info@digtiaalwerktuig.nl

=== Inventaire ===
Besides inventaire.io, inventaire team can setup, configure and maintain Wikibase instances. In 2019, the team worked with [https://github.com/abes-esr/poc-fne-wikibase-docker/tree/poc-fne BNF and ABES] to setup a proof of concept based on Wikibase
* Website: [https://inventaire.io Inventaire]
* Email: hello@inventaire.io

=== IP-Squared ===
IP Squared provides strategic information advice. IP Squared is specialised in projects around access to information, knowledge and culture. IP Squared works for public institutions such as (local) governments and heritage institutions. Projects by IP Squared are about legal and technological challenges around information and knowledge management, including intellectual property, data architecture, data modelling, linked open data, etc.

IP Squared is wholly owned by Maarten Zeinstra, LL.M. M.Sc.

* Website: {{sortkey|IP-Squared|[https://www.ip-squared.com/ IP-Squared]}}
* Email: info@ip-squared.com

=== Knowledge Management Associates ===
Consulting and implementation of Wikibase & Semantic MediaWiki solutions. Linking data with Wikidata.

* Website: [https://km-a.net/knowledge-wiki/ KM-A (Knowledge Management Associates)]
* Email: bernhard.krabina@km-a.net

=== Micelio ===
Micelio is involved in various implementation and research projects on using Wikidata. Most notably the Gene Wiki project where biomedical public databases are aligned with Wikidata. While Wikidata remains core, various use cases emerged where data is not eligible for inclusion in Wikidata (e.g. non-public reuse licenses or in need of a data model that is not yet implemented on Wikidata). In close collaboration with others we then explore the possibilities of deploying and reusing wikibase to allow creating a federated landscape of deployed wikibases that have Wikidata as a core. This through running Proof-of-concept studies or assisting in "Bring your own data" workshops, where participants are assisted in adding their data to a wikibase.

* Website: {{sortkey|Micelio|[http://www.micelio.be Micelio]}}
* Email: andra@micel.io

=== The QA Company ===
We are currently maintaining the Wikibase infrastructure of the European Commission at https://linkedopendata.eu. This includes setup, installation of extensions, customisation of logos, login with oAuth and more. We are also integrating data of the European Commission about countries, capitals, head of states, buildings, projects financed by the Commission and many more. The Wikibase is currently feeding different services like [https://kohesio.eu this public website]. Do not hesitate to contact us!

Our Wikibase data modelling expertise includes: deep knowledge of semantic modelling, the ability to reuse entities from Wikidata in local installations, keeping knowledge imported from Wikidata fresh, linking customer entities with Wikidata entities to profit from the efforts made by the Wikidata community.

* Website: [https://the-qa-company.com The QA Company]
* Email: info@qanswer.eu

=== Scatter ===
[[User:Harej|James Hare]] has been tinkering with custom Wikibases since 2015. Whatever the state of your data, get it fit for Wikidata, custom Wikibase, or interoperability with Wikidata. Wikidata and Wikipedia community relations. Private Wikidata query service. Registered in [https://sam.gov SAM] as a government contractor.

* Website: [https://scatter.red Scatter]
* Email: james@scatter.red

=== Wiki Valley ===

* Website: Wiki Valley ([https://en.wiki-valley.com/ en]) ([https://wiki-valley.com/ fr])
* Email: contact [[File:Meuble héraldique arobase.svg|22x22px]]wiki-valley.com

=== The Wikibase Consultancy ===

* Also known as [https://professional.wiki Professional Wiki]
* [https://professional.wiki/en/hosting/wikibase Tailored Wikibase hosting] and [https://www.pro.wiki/wikibase-hosting Wikibase cloud hosting]
* [https://www.wikibase.consulting/about-the-wikibase-team/ Developer that created Wikibase] and [https://www.wikibase.consulting/blog/ multiple Wikibase extensions]
* 240+ wikis hosted, MediaWiki development for 15+ years, 48000+ code changes
* [https://professional.wiki/en/jobs We are hiring]
* <span style="white-space: nowrap">Website: [https://wikibase.consulting The Wikibase Consultancy]</span>
** {{sortkey|Professional.Wiki|Professional.Wiki [https://professional.wiki (en]) ([https://Professional.Wiki/de de])}}
* Email: info@professional.wiki

=== WikiTeq ===
Full-service Wikibase & MediaWiki solutions, including site setup, extension development, skin design, semantic technologies, hosting, and continued support. Headed by Ike Hecht.

* Website: [https://www.wikiteq.com/ WikiTeq]
* Email: contact@wikiteq.com

=== WikiWorks ===
We are a consulting company, formed in 2009, that implements MediaWiki solutions for clients large and small. Our founder, Yaron Koren, is a veteran MediaWiki programmer who is one of the key developers of so-called "Enterprise MediaWiki". On our staff we also have other MediaWiki developers, and people with significant experience implementing MediaWiki solutions.

* Website: [https://wikiworks.com/ WikiWorks]
* Email: [mailto:info@wikiworks.com info@wikiworks.com]

==See also==
* [[mw:Professional development and consulting|Professional development and consulting for MediaWiki]], on which Wikibase is based

[[Category:Wikibase]]

Wikibase/Consultants and Support Providers

2023-10-25T19:24:38Z

Bryandamon: /* More details */ Added WikiWorks

{{ambox|type=warning |text=This is not a page for job posts or job advertisements. If you need Wikibase help, contact the individual service provider or company personally and privately.}}

This page is intended to help you find help with your Wikibase if you need it. Inclusion of a service provider on these lists does not constitute an official endorsement by the Wikibase team.

The lists do not claim to be exhaustive. If you think you or your company should be listed on the page, you are welcome to add it yourself.

== Overview of providers ==

{| class="wikitable sortable mw-collapsible" style="width: 95%;"
|+
|-
! scope="col" |Name
! scope="col" |Location
! Wikibase operations and support
! Wikibase custom development
! Wikibase data modeling
! Wikidata consulting
|-
|{{sortkey|Digitaal Werktuig|[[#Digitaal Werktuig|Digitaal Werktuig]]}}
|{{sortkey|Netherlands, Amersfoort|Amerfoort, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Inventaire|[[#Inventaire|Inventaire]]}}
|{{sortkey|France, Lyon|Lyon, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
|{{sortkey|IP-Squared|[[#IP-Squared|IP-Squared]]}}
|{{sortkey|Netherlands, Amsterdam|Amsterdam, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Knowledge Management Associates|[[#Knowledge Management Associates|Knowledge Management Associates]]}}
|{{sortkey|Austria, Vienna|Vienna, Austria}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|
|-
|{{sortkey|Micelio|[[#Micelio|Micelio]]}}
|{{sortkey|Belgium, Antwerpen|Antwerpen, Belgium}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|QA Company, The|[[#The QA Company|The QA Company]]}}
|{{sortkey|France, Saint-Etienne|Saint-Etienne, France}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Scatter|[[#Scatter|Scatter]]}}
|United States
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Wiki Valley|[[#Wiki Valley|Wiki Valley]]}}
|{{sortkey|France, Paris|Paris, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
| {{sortkey|Wikibase Consultancy, The|[[#The Wikibase Consultancy|The Wikibase Consultancy]]}}
| {{sortkey|Germany, Berlin|Berlin, Germany}}
| [[File:Yes check.svg|15px|link=]]
| [[File:Yes check.svg|15px|link=]]
|
|
|-
|{{sortkey|WikiTeq|[[#WikiTeq|WikiTeq]]}}
|{{sortkey|United States, Florida, Boca Raton|Boca Raton, Florida, United States}}
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|
|
|}

==More details==

=== Digitaal Werktuig ===
Digitaal Werktuig helps clients to share digital information, knowledge and culture as broadly as possible. In doing so, Digital Werktuig contributes to an open society, with engaged citizens. Digitaal Werktuig advises and supports organisations, projects and initiatives on matters concerning information technology.

Digitaal Werktuig is a freelance enterprise founded by Maarten Brinkerink (Est. October 2020). Maarten Brinkerink is an expert in digital culture and information processing. He is an experienced project manager, researcher and consultant, working in the cultural heritage sector for 15 years. Next to his freelance activities, Maarten also works at the Netherlands Institute for Sound & Vision as an IT solution architect.

* Website: {{sortkey|Digitaal Werktuig|[http://www.digitaalwerktuig.nl/en Digitaal Werktuig]}}
* Email: info@digtiaalwerktuig.nl

=== Inventaire ===
Besides inventaire.io, inventaire team can setup, configure and maintain Wikibase instances. In 2019, the team worked with [https://github.com/abes-esr/poc-fne-wikibase-docker/tree/poc-fne BNF and ABES] to setup a proof of concept based on Wikibase
* Website: [https://inventaire.io Inventaire]
* Email: hello@inventaire.io

=== IP-Squared ===
IP Squared provides strategic information advice. IP Squared is specialised in projects around access to information, knowledge and culture. IP Squared works for public institutions such as (local) governments and heritage institutions. Projects by IP Squared are about legal and technological challenges around information and knowledge management, including intellectual property, data architecture, data modelling, linked open data, etc.

IP Squared is wholly owned by Maarten Zeinstra, LL.M. M.Sc.

* Website: {{sortkey|IP-Squared|[https://www.ip-squared.com/ IP-Squared]}}
* Email: info@ip-squared.com

=== Knowledge Management Associates ===
Consulting and implementation of Wikibase & Semantic MediaWiki solutions. Linking data with Wikidata.

* Website: [https://km-a.net/knowledge-wiki/ KM-A (Knowledge Management Associates)]
* Email: bernhard.krabina@km-a.net

=== Micelio ===
Micelio is involved in various implementation and research projects on using Wikidata. Most notably the Gene Wiki project where biomedical public databases are aligned with Wikidata. While Wikidata remains core, various use cases emerged where data is not eligible for inclusion in Wikidata (e.g. non-public reuse licenses or in need of a data model that is not yet implemented on Wikidata). In close collaboration with others we then explore the possibilities of deploying and reusing wikibase to allow creating a federated landscape of deployed wikibases that have Wikidata as a core. This through running Proof-of-concept studies or assisting in "Bring your own data" workshops, where participants are assisted in adding their data to a wikibase.

* Website: {{sortkey|Micelio|[http://www.micelio.be Micelio]}}
* Email: andra@micel.io

=== The QA Company ===
We are currently maintaining the Wikibase infrastructure of the European Commission at https://linkedopendata.eu. This includes setup, installation of extensions, customisation of logos, login with oAuth and more. We are also integrating data of the European Commission about countries, capitals, head of states, buildings, projects financed by the Commission and many more. The Wikibase is currently feeding different services like [https://kohesio.eu this public website]. Do not hesitate to contact us!

Our Wikibase data modelling expertise includes: deep knowledge of semantic modelling, the ability to reuse entities from Wikidata in local installations, keeping knowledge imported from Wikidata fresh, linking customer entities with Wikidata entities to profit from the efforts made by the Wikidata community.

* Website: [https://the-qa-company.com The QA Company]
* Email: info@qanswer.eu

=== Scatter ===
[[User:Harej|James Hare]] has been tinkering with custom Wikibases since 2015. Whatever the state of your data, get it fit for Wikidata, custom Wikibase, or interoperability with Wikidata. Wikidata and Wikipedia community relations. Private Wikidata query service. Registered in [https://sam.gov SAM] as a government contractor.

* Website: [https://scatter.red Scatter]
* Email: james@scatter.red

=== Wiki Valley ===

* Website: Wiki Valley ([https://en.wiki-valley.com/ en]) ([https://wiki-valley.com/ fr])
* Email: contact [[File:Meuble héraldique arobase.svg|22x22px]]wiki-valley.com

=== The Wikibase Consultancy ===

* Also known as [https://professional.wiki Professional Wiki]
* [https://professional.wiki/en/hosting/wikibase Tailored Wikibase hosting] and [https://www.pro.wiki/wikibase-hosting Wikibase cloud hosting]
* [https://www.wikibase.consulting/about-the-wikibase-team/ Developer that created Wikibase] and [https://www.wikibase.consulting/blog/ multiple Wikibase extensions]
* 240+ wikis hosted, MediaWiki development for 15+ years, 48000+ code changes
* [https://professional.wiki/en/jobs We are hiring]
* <span style="white-space: nowrap">Website: [https://wikibase.consulting The Wikibase Consultancy]</span>
** {{sortkey|Professional.Wiki|Professional.Wiki [https://professional.wiki (en]) ([https://Professional.Wiki/de de])}}
* Email: info@professional.wiki

=== WikiTeq ===
Full-service Wikibase & MediaWiki solutions, including site setup, extension development, skin design, semantic technologies, hosting, and continued support. Headed by Ike Hecht.

* Website: [https://www.wikiteq.com/ WikiTeq]
* Email: contact@wikiteq.com

=== WikiWorks ===
We are a consulting company, formed in 2009, that implements MediaWiki solutions for clients large and small. Our founder, Yaron Koren, is a veteran MediaWiki programmer who is one of the key developers of so-called "Enterprise MediaWiki". On our staff we also have other MediaWiki developers, and people with significant experience implementing MediaWiki solutions.

* Website: [https://wikiworks.com/ WikiWorks]
* Email: [mailto:info@wikiworks.com info@wikiworks.com]

==See also==
* [[mw:Professional development and consulting|Professional development and consulting for MediaWiki]], on which Wikibase is based

[[Category:Wikibase]]

Wikibase/Consultants and Support Providers

2023-10-25T19:21:05Z

Bryandamon: /* More details */ Sorted alphabetically.

{{ambox|type=warning |text=This is not a page for job posts or job advertisements. If you need Wikibase help, contact the individual service provider or company personally and privately.}}

This page is intended to help you find help with your Wikibase if you need it. Inclusion of a service provider on these lists does not constitute an official endorsement by the Wikibase team.

The lists do not claim to be exhaustive. If you think you or your company should be listed on the page, you are welcome to add it yourself.

== Overview of providers ==

{| class="wikitable sortable mw-collapsible" style="width: 95%;"
|+
|-
! scope="col" |Name
! scope="col" |Location
! Wikibase operations and support
! Wikibase custom development
! Wikibase data modeling
! Wikidata consulting
|-
|{{sortkey|Digitaal Werktuig|[[#Digitaal Werktuig|Digitaal Werktuig]]}}
|{{sortkey|Netherlands, Amersfoort|Amerfoort, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Inventaire|[[#Inventaire|Inventaire]]}}
|{{sortkey|France, Lyon|Lyon, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
|{{sortkey|IP-Squared|[[#IP-Squared|IP-Squared]]}}
|{{sortkey|Netherlands, Amsterdam|Amsterdam, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Knowledge Management Associates|[[#Knowledge Management Associates|Knowledge Management Associates]]}}
|{{sortkey|Austria, Vienna|Vienna, Austria}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|
|-
|{{sortkey|Micelio|[[#Micelio|Micelio]]}}
|{{sortkey|Belgium, Antwerpen|Antwerpen, Belgium}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|QA Company, The|[[#The QA Company|The QA Company]]}}
|{{sortkey|France, Saint-Etienne|Saint-Etienne, France}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Scatter|[[#Scatter|Scatter]]}}
|United States
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Wiki Valley|[[#Wiki Valley|Wiki Valley]]}}
|{{sortkey|France, Paris|Paris, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
| {{sortkey|Wikibase Consultancy, The|[[#The Wikibase Consultancy|The Wikibase Consultancy]]}}
| {{sortkey|Germany, Berlin|Berlin, Germany}}
| [[File:Yes check.svg|15px|link=]]
| [[File:Yes check.svg|15px|link=]]
|
|
|-
|{{sortkey|WikiTeq|[[#WikiTeq|WikiTeq]]}}
|{{sortkey|United States, Florida, Boca Raton|Boca Raton, Florida, United States}}
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|
|
|}

==More details==

=== Digitaal Werktuig ===
Digitaal Werktuig helps clients to share digital information, knowledge and culture as broadly as possible. In doing so, Digital Werktuig contributes to an open society, with engaged citizens. Digitaal Werktuig advises and supports organisations, projects and initiatives on matters concerning information technology.

Digitaal Werktuig is a freelance enterprise founded by Maarten Brinkerink (Est. October 2020). Maarten Brinkerink is an expert in digital culture and information processing. He is an experienced project manager, researcher and consultant, working in the cultural heritage sector for 15 years. Next to his freelance activities, Maarten also works at the Netherlands Institute for Sound & Vision as an IT solution architect.

* Website: {{sortkey|Digitaal Werktuig|[http://www.digitaalwerktuig.nl/en Digitaal Werktuig]}}
* Email: info@digtiaalwerktuig.nl

=== Inventaire ===
Besides inventaire.io, inventaire team can setup, configure and maintain Wikibase instances. In 2019, the team worked with [https://github.com/abes-esr/poc-fne-wikibase-docker/tree/poc-fne BNF and ABES] to setup a proof of concept based on Wikibase
* Website: [https://inventaire.io Inventaire]
* Email: hello@inventaire.io

=== IP-Squared ===
IP Squared provides strategic information advice. IP Squared is specialised in projects around access to information, knowledge and culture. IP Squared works for public institutions such as (local) governments and heritage institutions. Projects by IP Squared are about legal and technological challenges around information and knowledge management, including intellectual property, data architecture, data modelling, linked open data, etc.

IP Squared is wholly owned by Maarten Zeinstra, LL.M. M.Sc.

* Website: {{sortkey|IP-Squared|[https://www.ip-squared.com/ IP-Squared]}}
* Email: info@ip-squared.com

=== Knowledge Management Associates ===
Consulting and implementation of Wikibase & Semantic MediaWiki solutions. Linking data with Wikidata.

* Website: [https://km-a.net/knowledge-wiki/ KM-A (Knowledge Management Associates)]
* Email: bernhard.krabina@km-a.net

=== Micelio ===
Micelio is involved in various implementation and research projects on using Wikidata. Most notably the Gene Wiki project where biomedical public databases are aligned with Wikidata. While Wikidata remains core, various use cases emerged where data is not eligible for inclusion in Wikidata (e.g. non-public reuse licenses or in need of a data model that is not yet implemented on Wikidata). In close collaboration with others we then explore the possibilities of deploying and reusing wikibase to allow creating a federated landscape of deployed wikibases that have Wikidata as a core. This through running Proof-of-concept studies or assisting in "Bring your own data" workshops, where participants are assisted in adding their data to a wikibase.

* Website: {{sortkey|Micelio|[http://www.micelio.be Micelio]}}
* Email: andra@micel.io

=== The QA Company ===
We are currently maintaining the Wikibase infrastructure of the European Commission at https://linkedopendata.eu. This includes setup, installation of extensions, customisation of logos, login with oAuth and more. We are also integrating data of the European Commission about countries, capitals, head of states, buildings, projects financed by the Commission and many more. The Wikibase is currently feeding different services like [https://kohesio.eu this public website]. Do not hesitate to contact us!

Our Wikibase data modelling expertise includes: deep knowledge of semantic modelling, the ability to reuse entities from Wikidata in local installations, keeping knowledge imported from Wikidata fresh, linking customer entities with Wikidata entities to profit from the efforts made by the Wikidata community.

* Website: [https://the-qa-company.com The QA Company]
* Email: info@qanswer.eu

=== Scatter ===
[[User:Harej|James Hare]] has been tinkering with custom Wikibases since 2015. Whatever the state of your data, get it fit for Wikidata, custom Wikibase, or interoperability with Wikidata. Wikidata and Wikipedia community relations. Private Wikidata query service. Registered in [https://sam.gov SAM] as a government contractor.

* Website: [https://scatter.red Scatter]
* Email: james@scatter.red

=== Wiki Valley ===

* Website: Wiki Valley ([https://en.wiki-valley.com/ en]) ([https://wiki-valley.com/ fr])
* Email: contact [[File:Meuble héraldique arobase.svg|22x22px]]wiki-valley.com

=== The Wikibase Consultancy ===

* Also known as [https://professional.wiki Professional Wiki]
* [https://professional.wiki/en/hosting/wikibase Tailored Wikibase hosting] and [https://www.pro.wiki/wikibase-hosting Wikibase cloud hosting]
* [https://www.wikibase.consulting/about-the-wikibase-team/ Developer that created Wikibase] and [https://www.wikibase.consulting/blog/ multiple Wikibase extensions]
* 240+ wikis hosted, MediaWiki development for 15+ years, 48000+ code changes
* [https://professional.wiki/en/jobs We are hiring]
* <span style="white-space: nowrap">Website: [https://wikibase.consulting The Wikibase Consultancy]</span>
** {{sortkey|Professional.Wiki|Professional.Wiki [https://professional.wiki (en]) ([https://Professional.Wiki/de de])}}
* Email: info@professional.wiki

=== WikiTeq ===
Full-service Wikibase & MediaWiki solutions, including site setup, extension development, skin design, semantic technologies, hosting, and continued support. Headed by Ike Hecht.

* Website: [https://www.wikiteq.com/ WikiTeq]
* Email: contact@wikiteq.com

==See also==
* [[mw:Professional development and consulting|Professional development and consulting for MediaWiki]], on which Wikibase is based

[[Category:Wikibase]]

Wikibase/Consultants and Support Providers

2023-10-25T19:08:26Z

Bryandamon: /* Overview of providers */ Alphabetic sorting by default.

{{ambox|type=warning |text=This is not a page for job posts or job advertisements. If you need Wikibase help, contact the individual service provider or company personally and privately.}}

This page is intended to help you find help with your Wikibase if you need it. Inclusion of a service provider on these lists does not constitute an official endorsement by the Wikibase team.

The lists do not claim to be exhaustive. If you think you or your company should be listed on the page, you are welcome to add it yourself.

== Overview of providers ==

{| class="wikitable sortable mw-collapsible" style="width: 95%;"
|+
|-
! scope="col" |Name
! scope="col" |Location
! Wikibase operations and support
! Wikibase custom development
! Wikibase data modeling
! Wikidata consulting
|-
|{{sortkey|Digitaal Werktuig|[[#Digitaal Werktuig|Digitaal Werktuig]]}}
|{{sortkey|Netherlands, Amersfoort|Amerfoort, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Inventaire|[[#Inventaire|Inventaire]]}}
|{{sortkey|France, Lyon|Lyon, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
|{{sortkey|IP-Squared|[[#IP-Squared|IP-Squared]]}}
|{{sortkey|Netherlands, Amsterdam|Amsterdam, Netherlands}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Knowledge Management Associates|[[#Knowledge Management Associates|Knowledge Management Associates]]}}
|{{sortkey|Austria, Vienna|Vienna, Austria}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|
|-
|{{sortkey|Micelio|[[#Micelio|Micelio]]}}
|{{sortkey|Belgium, Antwerpen|Antwerpen, Belgium}}
|
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|QA Company, The|[[#The QA Company|The QA Company]]}}
|{{sortkey|France, Saint-Etienne|Saint-Etienne, France}}
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Scatter|[[#Scatter|Scatter]]}}
|United States
|[[File:Yes check.svg|15px|link=]]
|
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|-
|{{sortkey|Wiki Valley|[[#Wiki Valley|Wiki Valley]]}}
|{{sortkey|France, Paris|Paris, France}}
|[[File:Yes check.svg|15px|link=]]
|
|
|
|-
| {{sortkey|Wikibase Consultancy, The|[[#The Wikibase Consultancy|The Wikibase Consultancy]]}}
| {{sortkey|Germany, Berlin|Berlin, Germany}}
| [[File:Yes check.svg|15px|link=]]
| [[File:Yes check.svg|15px|link=]]
|
|
|-
|{{sortkey|WikiTeq|[[#WikiTeq|WikiTeq]]}}
|{{sortkey|United States, Florida, Boca Raton|Boca Raton, Florida, United States}}
|[[File:Yes check.svg|15px|link=]]
|[[File:Yes check.svg|15px|link=]]
|
|
|}

==More details==

=== The Wikibase Consultancy ===

* Also known as [https://professional.wiki Professional Wiki]
* [https://professional.wiki/en/hosting/wikibase Tailored Wikibase hosting] and [https://www.pro.wiki/wikibase-hosting Wikibase cloud hosting]
* [https://www.wikibase.consulting/about-the-wikibase-team/ Developer that created Wikibase] and [https://www.wikibase.consulting/blog/ multiple Wikibase extensions]
* 240+ wikis hosted, MediaWiki development for 15+ years, 48000+ code changes
* [https://professional.wiki/en/jobs We are hiring]
* <span style="white-space: nowrap">Website: [https://wikibase.consulting The Wikibase Consultancy]</span>
** {{sortkey|Professional.Wiki|Professional.Wiki [https://professional.wiki (en]) ([https://Professional.Wiki/de de])}}
* Email: info@professional.wiki

=== Inventaire ===
Besides inventaire.io, inventaire team can setup, configure and maintain Wikibase instances. In 2019, the team worked with [https://github.com/abes-esr/poc-fne-wikibase-docker/tree/poc-fne BNF and ABES] to setup a proof of concept based on Wikibase
* Website: [https://inventaire.io Inventaire]
* Email: hello@inventaire.io

=== Knowledge Management Associates ===
Consulting and implementation of Wikibase & Semantic MediaWiki solutions. Linking data with Wikidata.

* Website: [https://km-a.net/knowledge-wiki/ KM-A (Knowledge Management Associates)]
* Email: bernhard.krabina@km-a.net

=== Micelio ===
Micelio is involved in various implementation and research projects on using Wikidata. Most notably the Gene Wiki project where biomedical public databases are aligned with Wikidata. While Wikidata remains core, various use cases emerged where data is not eligible for inclusion in Wikidata (e.g. non-public reuse licenses or in need of a data model that is not yet implemented on Wikidata). In close collaboration with others we then explore the possibilities of deploying and reusing wikibase to allow creating a federated landscape of deployed wikibases that have Wikidata as a core. This through running Proof-of-concept studies or assisting in "Bring your own data" workshops, where participants are assisted in adding their data to a wikibase.

* Website: {{sortkey|Micelio|[http://www.micelio.be Micelio]}}
* Email: andra@micel.io

=== IP-Squared ===
IP Squared provides strategic information advice. IP Squared is specialised in projects around access to information, knowledge and culture. IP Squared works for public institutions such as (local) governments and heritage institutions. Projects by IP Squared are about legal and technological challenges around information and knowledge management, including intellectual property, data architecture, data modelling, linked open data, etc.

IP Squared is wholly owned by Maarten Zeinstra, LL.M. M.Sc.

* Website: {{sortkey|IP-Squared|[https://www.ip-squared.com/ IP-Squared]}}
* Email: info@ip-squared.com

=== Digitaal Werktuig ===
Digitaal Werktuig helps clients to share digital information, knowledge and culture as broadly as possible. In doing so, Digital Werktuig contributes to an open society, with engaged citizens. Digitaal Werktuig advises and supports organisations, projects and initiatives on matters concerning information technology.

Digitaal Werktuig is a freelance enterprise founded by Maarten Brinkerink (Est. October 2020). Maarten Brinkerink is an expert in digital culture and information processing. He is an experienced project manager, researcher and consultant, working in the cultural heritage sector for 15 years. Next to his freelance activities, Maarten also works at the Netherlands Institute for Sound & Vision as an IT solution architect.

* Website: {{sortkey|Digitaal Werktuig|[http://www.digitaalwerktuig.nl/en Digitaal Werktuig]}}
* Email: info@digtiaalwerktuig.nl

=== The QA Company ===
We are currently maintaining the Wikibase infrastructure of the European Commission at https://linkedopendata.eu. This includes setup, installation of extensions, customisation of logos, login with oAuth and more. We are also integrating data of the European Commission about countries, capitals, head of states, buildings, projects financed by the Commission and many more. The Wikibase is currently feeding different services like [https://kohesio.eu this public website]. Do not hesitate to contact us!

Our Wikibase data modelling expertise includes: deep knowledge of semantic modelling, the ability to reuse entities from Wikidata in local installations, keeping knowledge imported from Wikidata fresh, linking customer entities with Wikidata entities to profit from the efforts made by the Wikidata community.

* Website: [https://the-qa-company.com The QA Company]
* Email: info@qanswer.eu

=== Scatter ===
[[User:Harej|James Hare]] has been tinkering with custom Wikibases since 2015. Whatever the state of your data, get it fit for Wikidata, custom Wikibase, or interoperability with Wikidata. Wikidata and Wikipedia community relations. Private Wikidata query service. Registered in [https://sam.gov SAM] as a government contractor.

* Website: [https://scatter.red Scatter]
* Email: james@scatter.red

=== Wiki Valley ===

* Website: Wiki Valley ([https://en.wiki-valley.com/ en]) ([https://wiki-valley.com/ fr])
* Email: contact [[File:Meuble héraldique arobase.svg|22x22px]]wiki-valley.com

=== WikiTeq ===
Full-service Wikibase & MediaWiki solutions, including site setup, extension development, skin design, semantic technologies, hosting, and continued support. Headed by Ike Hecht.

* Website: [https://www.wikiteq.com/ WikiTeq]
* Email: contact@wikiteq.com

==See also==
* [[mw:Professional development and consulting|Professional development and consulting for MediaWiki]], on which Wikibase is based

[[Category:Wikibase]]

North American Hub Research Project

2023-07-24T02:58:27Z

Bryandamon: /* Members - Phase 1 */ Added my name.

{{Template:NAHub}}
==Overview==
In April 2023, [[Wikimedia DC]] was awarded a grant from the [[Wikimedia Foundation]] for the purpose of researching the feasibility of creating a North American Hub. A potential hub would consist of Wikimedia's North American affiliates, chapters, and user groups.

'''[[Grants:Project/MSIG/Researching a North American Hub|View the proposal]]'''

From May to December of 2023, a committee of representatives from North American chapters, affiliates and user groups, with administrative assistance from Wikimedia DC, will work to identify opportunities and barriers to movement participants across the North American continent in order to discuss and recommend service and support measures most useful to the community. A research-based assessment of the issues and challenges will serve as a basis for possibly initiating a North American Hub as an effective support organization for communities, affiliates, and contributors.

Research through virtual means will focus on the opportunities and needs for North American Wikimedians in the U.S., Mexico, Canada, and the Caribbean.

==Admin team, Wikimedia DC==
* [[User: Ariel Cetrone (WMDC)|Ariel Cetrone]] Institutional Partnerships Manager
* [[User:econterms|Peter Meyer]], President
* [[User:Sarasays|Sara Snyder]], Treasurer

==Advisory Committee==
There will be two project committees, one for each phase of planning.

The '''Phase One Committee''' consists of delegated representatives from a number of existing North American Affiliates. By August 2023, the committee will nominate additional active North American Wikimedians with an eye on achieving a balanced, diverse, and truly representative Phase 2 committee.

===Members - Phase 1===
* [[User:Pharos|Pharos]], [[Wikimedia New York City]]
* [[User:Bluerasberry|Bluerasberry]], [[Wikimedia LGBT+]] and [[Wikimedia Medicine]]
* [[User:Shanluan|Sherry Antoine]], [https://afrocrowd.org/ AfroCrowd] and [[Wikimedians of the Caribbean User Group]]
* [[User:Peaceray|Peaceray]], [[Cascadia Wikimedians]]
* [[User:Louis Germain (WMCA)|Louis Germain (WMCA)]]
* Kira Wisniewski, [[Art+Feminism]]
* [[User:Frank Schulenburg|Frank Schulenburg]], [[Wiki Education Foundation]]
* [[User:Dorevabelfiore | Doreva Belfiore]], [https://en.wikipedia.org/wiki/Wikipedia:Meetup/Philadelphia Philadelphia WikiSalon]
* [[User:Sj|SJ]], [[New England Wikimedians|New England Wikimedians (NEW)]]
* [[User:Rosiestep|Rosiestep]], [[WikiWomen's User Group]]
* James Udan, San Diego Wikimedians (tentatively)
* [[User:Bryandamon|Bryan Hilderbrand]], [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]]

===Members - Phase 2===
We are adding members:
* [[User:Lunita28mx|Lunita28mx]] of [[Wikimedia México]]
* [[User:Omar sansi|Omar Sansi]] of [[Wikimedia México]]

Small wiki toolkits/Workshops

2022-02-01T03:44:18Z

Bryandamon: /* How to maintain bots */ Signed up.

{{Notice|The first set of workshops for 2022 focuses on script and bot development, kicking off with an introduction to the Pywikibot framework and installation on '''Friday, February 25th, 2022, from 16:00 to 17:00 (UTC)'''. [[Small wiki toolkits/Workshops#Intro to Pywikibot framework and installation|'''Sign-up below to attend''']].}}

[[File:Participants of "Writing Wikidata queries" workshop at SWT Indic Workshop Series 2020.png|thumb|Participants of a small wiki toolkits virtual training|394x394px]]

== Overview ==
{{bulb}} '''Want to learn new technical skills to help improve your wiki? Sign-up for the workshops below!'''

These workshops cover a broad range of technical topics and build upon the lessons learned from the two regional initiatives organized in 2021: [[Small wiki toolkits/South Asia|South Asia]] and the [[Small wiki toolkits/Kurdish Wikimedians|Kurdish Wikimedians]]. [[mw:Developer_Advocacy|WMF's Developer Advocacy]] team coordinates this project. A 1—3 hour long workshop happens every month on a technical topic. The organizing team chooses topics based on the needs of smaller language wiki communities' and trainers' availability.

The first set of workshops for 2022 are geared towards script and bot development to help individuals learn how to automate work in their community via bots and develop, maintain, host them. If you are interested in proposing a topic, please share your ideas on the talk page.

== Upcoming workshops ==
Please add your signature under the workshops you would like to attend. More details will be shared with you closer to the date and time of a workshop in a message format on your talk page.

=== Intro to Pywikibot framework and installation ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/2</div>
*'''Description:''' In this workshop, participants will learn about the Pywikibot framework and how to install and configure it.
*'''Date & Time:''' [https://zonestamp.toolforge.org/1645804809 Friday, February 25th 2022, 16:00 to 17:30 (UTC)]
* '''Join the meeting:''' [http://meet.google.com/qrt-chts-uyj http://meet.google.com/qrt-chts-uyj]
*'''Prerequisites:''' Basic familiarity with [https://www.python.org/ Python] and using command-line shells.
*'''Language(s):''' English
*'''Trainer(s):''' [[User:SSapaty (WMF)]]
*'''Recording:'''
*'''Notes:''' https://etherpad.wikimedia.org/p/swt-intro-to-pywikibot
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:43, 1 February 2022 (UTC)

=== Intro to Wikimedia Tools (PAWS, Quarry, WDQS) for running queries and scripts ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/3</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/4</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:43, 1 February 2022 (UTC)

=== How to write a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/5</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:44, 1 February 2022 (UTC)

=== How to interact with Wikidata via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/6</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a popular bot on your wiki ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/7</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to host a bot on Toolforge ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to maintain bots ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:44, 1 February 2022 (UTC)

== Organization ==
{| class="wikitable"
|-
!Username !! Role
|-
|[[User:SSethi (WMF)|SSethi (WMF)]] || Advisory and liaising with WMF
|-
|[[User:SSapaty (WMF)|SSapaty (WMF)]] || Advisory and liaising with WMF
|-
|[[User:Dnshitobu|Dnshitobu]] || Liaising with communities and projects primarily related to Dagbani Wikipedia
|-
|[[User:Jayprakash12345|Jay Prakash]] || Technical mentor and Indic community liaison
|-
|[[User:Kushared|Mohammed]] || Liaising with communities and projects primarily related to Kurdish wiki projects
|-
|}

[[Category:Small wiki toolkits]]

Small wiki toolkits/Workshops

2022-02-01T03:44:05Z

Bryandamon: /* How to write a basic script via Pywikibot */ Signed up.

{{Notice|The first set of workshops for 2022 focuses on script and bot development, kicking off with an introduction to the Pywikibot framework and installation on '''Friday, February 25th, 2022, from 16:00 to 17:00 (UTC)'''. [[Small wiki toolkits/Workshops#Intro to Pywikibot framework and installation|'''Sign-up below to attend''']].}}

[[File:Participants of "Writing Wikidata queries" workshop at SWT Indic Workshop Series 2020.png|thumb|Participants of a small wiki toolkits virtual training|394x394px]]

== Overview ==
{{bulb}} '''Want to learn new technical skills to help improve your wiki? Sign-up for the workshops below!'''

These workshops cover a broad range of technical topics and build upon the lessons learned from the two regional initiatives organized in 2021: [[Small wiki toolkits/South Asia|South Asia]] and the [[Small wiki toolkits/Kurdish Wikimedians|Kurdish Wikimedians]]. [[mw:Developer_Advocacy|WMF's Developer Advocacy]] team coordinates this project. A 1—3 hour long workshop happens every month on a technical topic. The organizing team chooses topics based on the needs of smaller language wiki communities' and trainers' availability.

The first set of workshops for 2022 are geared towards script and bot development to help individuals learn how to automate work in their community via bots and develop, maintain, host them. If you are interested in proposing a topic, please share your ideas on the talk page.

== Upcoming workshops ==
Please add your signature under the workshops you would like to attend. More details will be shared with you closer to the date and time of a workshop in a message format on your talk page.

=== Intro to Pywikibot framework and installation ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/2</div>
*'''Description:''' In this workshop, participants will learn about the Pywikibot framework and how to install and configure it.
*'''Date & Time:''' [https://zonestamp.toolforge.org/1645804809 Friday, February 25th 2022, 16:00 to 17:30 (UTC)]
* '''Join the meeting:''' [http://meet.google.com/qrt-chts-uyj http://meet.google.com/qrt-chts-uyj]
*'''Prerequisites:''' Basic familiarity with [https://www.python.org/ Python] and using command-line shells.
*'''Language(s):''' English
*'''Trainer(s):''' [[User:SSapaty (WMF)]]
*'''Recording:'''
*'''Notes:''' https://etherpad.wikimedia.org/p/swt-intro-to-pywikibot
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:43, 1 February 2022 (UTC)

=== Intro to Wikimedia Tools (PAWS, Quarry, WDQS) for running queries and scripts ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/3</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/4</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:43, 1 February 2022 (UTC)

=== How to write a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/5</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:44, 1 February 2022 (UTC)

=== How to interact with Wikidata via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/6</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a popular bot on your wiki ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/7</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to host a bot on Toolforge ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to maintain bots ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

== Organization ==
{| class="wikitable"
|-
!Username !! Role
|-
|[[User:SSethi (WMF)|SSethi (WMF)]] || Advisory and liaising with WMF
|-
|[[User:SSapaty (WMF)|SSapaty (WMF)]] || Advisory and liaising with WMF
|-
|[[User:Dnshitobu|Dnshitobu]] || Liaising with communities and projects primarily related to Dagbani Wikipedia
|-
|[[User:Jayprakash12345|Jay Prakash]] || Technical mentor and Indic community liaison
|-
|[[User:Kushared|Mohammed]] || Liaising with communities and projects primarily related to Kurdish wiki projects
|-
|}

[[Category:Small wiki toolkits]]

Small wiki toolkits/Workshops

2022-02-01T03:43:50Z

Bryandamon: /* How to run a basic script via Pywikibot */ Signed up.

{{Notice|The first set of workshops for 2022 focuses on script and bot development, kicking off with an introduction to the Pywikibot framework and installation on '''Friday, February 25th, 2022, from 16:00 to 17:00 (UTC)'''. [[Small wiki toolkits/Workshops#Intro to Pywikibot framework and installation|'''Sign-up below to attend''']].}}

[[File:Participants of "Writing Wikidata queries" workshop at SWT Indic Workshop Series 2020.png|thumb|Participants of a small wiki toolkits virtual training|394x394px]]

== Overview ==
{{bulb}} '''Want to learn new technical skills to help improve your wiki? Sign-up for the workshops below!'''

These workshops cover a broad range of technical topics and build upon the lessons learned from the two regional initiatives organized in 2021: [[Small wiki toolkits/South Asia|South Asia]] and the [[Small wiki toolkits/Kurdish Wikimedians|Kurdish Wikimedians]]. [[mw:Developer_Advocacy|WMF's Developer Advocacy]] team coordinates this project. A 1—3 hour long workshop happens every month on a technical topic. The organizing team chooses topics based on the needs of smaller language wiki communities' and trainers' availability.

The first set of workshops for 2022 are geared towards script and bot development to help individuals learn how to automate work in their community via bots and develop, maintain, host them. If you are interested in proposing a topic, please share your ideas on the talk page.

== Upcoming workshops ==
Please add your signature under the workshops you would like to attend. More details will be shared with you closer to the date and time of a workshop in a message format on your talk page.

=== Intro to Pywikibot framework and installation ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/2</div>
*'''Description:''' In this workshop, participants will learn about the Pywikibot framework and how to install and configure it.
*'''Date & Time:''' [https://zonestamp.toolforge.org/1645804809 Friday, February 25th 2022, 16:00 to 17:30 (UTC)]
* '''Join the meeting:''' [http://meet.google.com/qrt-chts-uyj http://meet.google.com/qrt-chts-uyj]
*'''Prerequisites:''' Basic familiarity with [https://www.python.org/ Python] and using command-line shells.
*'''Language(s):''' English
*'''Trainer(s):''' [[User:SSapaty (WMF)]]
*'''Recording:'''
*'''Notes:''' https://etherpad.wikimedia.org/p/swt-intro-to-pywikibot
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:43, 1 February 2022 (UTC)

=== Intro to Wikimedia Tools (PAWS, Quarry, WDQS) for running queries and scripts ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/3</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/4</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:43, 1 February 2022 (UTC)

=== How to write a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/5</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to interact with Wikidata via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/6</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a popular bot on your wiki ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/7</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to host a bot on Toolforge ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to maintain bots ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

== Organization ==
{| class="wikitable"
|-
!Username !! Role
|-
|[[User:SSethi (WMF)|SSethi (WMF)]] || Advisory and liaising with WMF
|-
|[[User:SSapaty (WMF)|SSapaty (WMF)]] || Advisory and liaising with WMF
|-
|[[User:Dnshitobu|Dnshitobu]] || Liaising with communities and projects primarily related to Dagbani Wikipedia
|-
|[[User:Jayprakash12345|Jay Prakash]] || Technical mentor and Indic community liaison
|-
|[[User:Kushared|Mohammed]] || Liaising with communities and projects primarily related to Kurdish wiki projects
|-
|}

[[Category:Small wiki toolkits]]

Small wiki toolkits/Workshops

2022-02-01T03:43:27Z

Bryandamon: /* Intro to Pywikibot framework and installation */ Signed up.

{{Notice|The first set of workshops for 2022 focuses on script and bot development, kicking off with an introduction to the Pywikibot framework and installation on '''Friday, February 25th, 2022, from 16:00 to 17:00 (UTC)'''. [[Small wiki toolkits/Workshops#Intro to Pywikibot framework and installation|'''Sign-up below to attend''']].}}

[[File:Participants of "Writing Wikidata queries" workshop at SWT Indic Workshop Series 2020.png|thumb|Participants of a small wiki toolkits virtual training|394x394px]]

== Overview ==
{{bulb}} '''Want to learn new technical skills to help improve your wiki? Sign-up for the workshops below!'''

These workshops cover a broad range of technical topics and build upon the lessons learned from the two regional initiatives organized in 2021: [[Small wiki toolkits/South Asia|South Asia]] and the [[Small wiki toolkits/Kurdish Wikimedians|Kurdish Wikimedians]]. [[mw:Developer_Advocacy|WMF's Developer Advocacy]] team coordinates this project. A 1—3 hour long workshop happens every month on a technical topic. The organizing team chooses topics based on the needs of smaller language wiki communities' and trainers' availability.

The first set of workshops for 2022 are geared towards script and bot development to help individuals learn how to automate work in their community via bots and develop, maintain, host them. If you are interested in proposing a topic, please share your ideas on the talk page.

== Upcoming workshops ==
Please add your signature under the workshops you would like to attend. More details will be shared with you closer to the date and time of a workshop in a message format on your talk page.

=== Intro to Pywikibot framework and installation ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/2</div>
*'''Description:''' In this workshop, participants will learn about the Pywikibot framework and how to install and configure it.
*'''Date & Time:''' [https://zonestamp.toolforge.org/1645804809 Friday, February 25th 2022, 16:00 to 17:30 (UTC)]
* '''Join the meeting:''' [http://meet.google.com/qrt-chts-uyj http://meet.google.com/qrt-chts-uyj]
*'''Prerequisites:''' Basic familiarity with [https://www.python.org/ Python] and using command-line shells.
*'''Language(s):''' English
*'''Trainer(s):''' [[User:SSapaty (WMF)]]
*'''Recording:'''
*'''Notes:''' https://etherpad.wikimedia.org/p/swt-intro-to-pywikibot
</div>

Sign-up below to attend:
# [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 03:43, 1 February 2022 (UTC)

=== Intro to Wikimedia Tools (PAWS, Quarry, WDQS) for running queries and scripts ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/3</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/4</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to write a basic script via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/5</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to interact with Wikidata via Pywikibot ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/6</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to run a popular bot on your wiki ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/7</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to host a bot on Toolforge ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

=== How to maintain bots ===
<div style="border: 2px solid #06b; border-radius: 1em; margin: 1em; padding: 0; overflow: hidden;">
<div style="background-color: #06b; border-bottom-right-radius: 1em; color: #fff; font-weight: bold; font-size: 80%; text-transform: uppercase; text-align: center; width: 100px; cursor: default;">2022/8</div>
*'''Description:''' Coming soon
*'''Date & Time:''' TBD
* '''Join the meeting:'''
*'''Prerequisites:''' TBD
*'''Language(s):''' English
*'''Trainer(s):''' TBD
*'''Recording:'''
*'''Notes:'''
</div>

Sign-up below to attend:
# ...

== Organization ==
{| class="wikitable"
|-
!Username !! Role
|-
|[[User:SSethi (WMF)|SSethi (WMF)]] || Advisory and liaising with WMF
|-
|[[User:SSapaty (WMF)|SSapaty (WMF)]] || Advisory and liaising with WMF
|-
|[[User:Dnshitobu|Dnshitobu]] || Liaising with communities and projects primarily related to Dagbani Wikipedia
|-
|[[User:Jayprakash12345|Jay Prakash]] || Technical mentor and Indic community liaison
|-
|[[User:Kushared|Mohammed]] || Liaising with communities and projects primarily related to Kurdish wiki projects
|-
|}

[[Category:Small wiki toolkits]]

WikiCite/Shared Citations

2021-04-16T18:18:05Z

Bryandamon: /* Endorsements */ Added my endorsement.

{{Draft}}
{{nutshell|A proposal for a system for Shared Citations database as a "Commons for references", with associated software development to support its integration across Wikimedia projects.}}
{{ProjectInfobox
|name=Shared Citations
|summary=[[File:Webcomic xkcd - Wikipedian protester cropped.png|center|link=]]<br>A proposed database of Wikimedia citation records; and associated improvements to cross-wiki monitoring and editing.
|members=[[m:User:LWyatt (WMF)|Liam Wyatt]] (WMF – WikiCite)}}
This is a proposal for the Wikimedia Foundation to create a database of Wikimedia citation records; and associated improvements to cross-wiki monitoring and editing. These two pillars would empower community-managed workflows and tools to:<center>Make citations '''easier''' for the editor,<br>more '''useful''' for the reader,<br> and more '''efficient''' for our architecture.<br>
[[File:Shared_Citations.png|center|400px|link=]]</center>

== Overview ==
=== Problem statement ===
'''Citations are the core of verifiability, anti-disinformation and knowledge integrity in our movement. Ensuring Knowledge equity extends to ensuring representative diversity of references – forms, languages, and author demographics.'''<br>Our Verifiability policy has become the backbone of the reliable web. Wikimedia’s citations are one of our greatest assets. However, because of being stored as raw “inline” text in each content page, references are also one of our biggest burdens.<br>
'''Our references are high in maintenance, technical complexity, and duplication of effort. This results in knowledge gaps and biases that are difficult to quantify and address.'''<br>
This burden of reference creation and maintenance is shouldered by repetitive, manual, volunteer effort which is disproportionately felt by smaller communities.<br>In order to reach [[:File:Wikimedia 2030 Movement Strategy Recommendations in English.pdf|2030 goals]] of eliminating systematic knowledge and contributor demographic gaps, better systems for understanding, monitoring, and redressing these gaps are required.

{{Quote|text=Citations are a simple, critical interconnection mechanism for all modern knowledge in the digital, Internet-connected world... Arguably ''the most important ingredient of open knowledge'', sources and references have ironically received little technical attention in the Wikimedia movement up until now.|source=[[:File:WikiCite_2016_report.pdf|2016 WikiCite annual report]]}}
{{TOC right}}

Not only is there duplication of effort, but massive duplication of the content itself. According to March 2018 research, every source used in Wikipedia is cited approximately 3.5 times,<ref>https://medium.com/freely-sharing-the-sum-of-all-knowledge/what-are-the-ten-most-cited-sources-on-wikipedia-lets-ask-the-data-34071478785a</ref> and the most reused reference appeared across all Wikipedias more than 2.8 million times.<ref>https://hess.copernicus.org/articles/11/1633/2007/</ref> It is impossible to determined these numbers definitively precisely because of a lack of consistent or centralised citation management. At 450+ characters per citation, this results in ''at least'' 1 GB of HTML to refer to a single publication—hand curated by volunteers, often with semi-automated tools. Moreover, due to small stylistic variations and dataentry errors, there are probably many more instances of this one "single" citation unaccounted for. Wikimedia Commons was created in 2004 to host media files for all Wikipedias rather than having to reupload the same file to each language to reuse it; and yet in 2020 we still reinsert the same metadata every time we wish to reuse a footnote in a different page. <gallery mode="packed" heights="120px" caption="Examples of the status quo">
File:References status quo & Shared Citations records examples.pdf|page=2|A Wikipedia sentence with multiple references. In ''source'' editing view (without additional syntax highlighting) it is extremely difficult for humans to parse.
File:References status quo & Shared Citations records examples.pdf|page=3|A standard English Wikipedia reference, to our [https://medium.com/freely-sharing-the-sum-of-all-knowledge/what-are-the-ten-most-cited-sources-on-wikipedia-lets-ask-the-data-34071478785a most re-used citation]. Many variations of references to the same source exist, with slightly different fields or content.
File:References status quo & Shared Citations records examples.pdf|page=4|A French Wiktionary reference. The differences between the way in which different wiktionaries handle references is arguably even bigger than the differences between Wikipedias.
File:References status quo & Shared Citations records examples.pdf|page=5|Reference fields in Wikidata are edited independently. This is even when the same information is identical, on the same property, on the same item.
File:References status quo & Shared Citations records examples.pdf|page=6|Each ''field'' of each Wikidata reference is stored independently, even if it’s identical.
</gallery>

=== Background ===
[[File:WikiCite 2017 participants 1.jpg|thumb|Wikimedians have been thinking about how to handle citations for many years... – ''[[WikiCite]] Conf (2017)'']]
Many proposals have been made for centralising and simplifying reference management in Wikimedia projects, [[Wikicite (metadata proposal)|since at least as early as 2005]]. There are also various methods currently in use which try to reduce both the visual complexity of the sourcecode, and the workload of curating frequently reused references. These include:
* [[w:en:Category:Specific-source templates|Specific source templates]] – many Wikipedias. Template pages for hosting the citation details of a specific source, inserted directly into an article.
* [[w:en:Template:Cite Q|Cite Q template]] – several Wikipedias. A citation template which, when inserted, calls upon a nominated Wikidata item to display the source metadata.
*[[w:fr:Aide:Espace_r%C3%A9f%C3%A9rence|References namespace]] – French Wikipedia. A specific namespace where all notable published editions of popular works and authors are collated for easy comparison.
With the launch of Wikidata as a technical solution for representing and managing structured data in a single, centralised knowledge base, the [[WikiCite]] initiative was launched in 2016. [[WikiCite/administration|Supported by the WMF, several Wikimedia affiliates, technical and philanthropic organisations]], the initiative's aim was to foster a community of people and ecosystem of projects to support workflows, tools, datamodels, and best practices that seed a '''universal repository of open bibliographic data of citable sources within Wikidata'''. Aside from engaging a broad community of volunteers, tools developers, library and GLAM professionals, and linked data experts, the WikiCite initiative succeeded at creating a very large corpus of well-modelled items about sources in Wikidata, including 36+ million items about scholarly articles and 26+ million items with a DOI.<ref>https://zenodo.org/record/4121846#.X8kPsmRKiog</ref> It also showcased the power of running large scale queries and analyses on this bibliographic corpus using the Wikidata Query Service with services such as [https://scholia.toolforge.org/ Scholia].

However, the practical use of the WikiCite corpus as a resource for supporting citation management in Wikimedia projects (including Wikidata itself) has been hindered by multiple factors including, but not limited to:
* the difficulty of mapping individual sources used as references in Wikimedia projects' pages to the corresponding Wikidata items about their works, authors, publishers, main subject.
* the lack of tools to transparently monitor how changes made in Wikidata propagate to other wikis (for example when metadata used in Wikidata are used to populate reference templates in a Wikipedia article).
* the lack of solutions to integrate Wikidata with tools like Citoid, which enormously reduce barriers to create new references in Wikipedia articles.

* the undesirability of storing the sheer volume of sources that are used in Wikipedia and sister projects as individual Wikidata items. For example, tens of millions of items about individual URLs and newspaper articles.
* the lack of a good definition of "completeness", making the project very open-ended and its [[wikidata:Wikidata:WikiCite/Roadmap|scope]] unclear.
While the WikiCite initiative has demonstrated the value of creating and managing a rich database of sources in Wikidata, through the development of countless tools and applications that leverage its data or facilitate its curation, '''Wikidata's practical use to support the daily needs of volunteer editors working on references in Wikimedia projects has not been realized to date'''. What has been missing so far is a bridging layer that enables managing references in individual Wikipedia projects, while connecting them to the rich, structured information about these sources, authors, publishers, main subjects etc. that exists in Wikidata.

=== Shared Citations ===
'''Shared Citations''' is a proposed new database, aiming to centralise the hosting and metadata-management of individual references used in any Wikimedia project as structured data "records". Each Wikimedia project could then call upon these records and, according to its own citation style preferences, display them to their readers.

By '''centralising''', '''structuring''', and '''sharing''' the content, the following can be achieved:

* much duplication of content curation effort can be reduced
* many workflows which improve knowledge integrity can benefit all sister projects simultaneously
* new processes and research can be undertaken to improve increase our understanding of Wikimedia references; and
* the architecture of how we store and update reference information can be made much more efficient.

Additionally, this proposed database would enable linking entities mentioned in its records (authors, publishers, main subject, journals, etc.) to the corresponding Wikidata items, making cross-language reconciliation and the analysis of sources across projects a practical possibility. This would enable significant research (both internal, and academic) to be undertaken for the first time.

====Examples of how a Shared Citation record ''might'' work====

[[File:References status quo & Shared Citations records examples.pdf|page=7|thumb|400px|A citation record of a '''book''' edition]]
Of note in the '''Book''' example:
* References to different editions of the same work could be linked to each other.
* References to different sub-sections of the same work (e.g. Page/pagerange/Chapter) can be combined into one Shared Citation record, providing faceted search.
* That multiple references to the same citation record can be sorted and grouped in many ways. By extension, different content management workflows can be created.
{{-}}
[[File:References status quo & Shared Citations records examples.pdf|page=8|thumb|400px|A citation record of a scholarly '''journal article'''.]]
Of note in '''journal article''' example:
* The difference between an author's name (as described on the publication itself), the Wikidata item for that author, and any given structured format (F.Last/First Last/Last, M. First) that we might like to display to our readers.
* The ability to store and update the various ways which a source might be accessed by different users (e.g. for free, or those with academic institutional logins).
* Easy and precise access to version(s) of a citation record can be maintained.
* The ability to know a source's status (e.g. preprint, peer review published, self-published, retracted). By extension, to treat the reference differently as a result.
* Traceability of where in use, or former, instances of references to a citation record are used in Wikimedia projects.
{{-}}
[[File:References status quo & Shared Citations records examples.pdf|page=9|thumb|400px|A citation record of a '''newspaper article'''.]]
Of note in '''newspaper article''' example:
* The capacity to identify frequently reused text strings (author, publisher...) which have no Wikidata item as creation-candidates, yet still be able to host citations which refer to them.
* Different citations which refer to the same author/publisher/location/publication date (etc.) across Wikimedia project can be searched and filtered.
* That Wikimedia editing campaigns which worked with any given citation could be identified.
{{-}}
[[File:References status quo & Shared Citations records examples.pdf|page=10|thumb|400px|A ''hypothetical'' implementation of a '''reference template''' in Source editor mode.]]
Of note in '''reference template''' example:
* The reference's content and format for the reader is independent of the data. The display format could be determined by the choice of citation template, or a parameter in that template.
* Quick and easy access to where the citation record "lives" is provided in any editing environment (see [[#Principles]] below)
* The ability to have locally hosted "freetext" fields which could include contextual information not stored in the central citation record. Equally, the ability to "suppress" centrally hosted fields and replace with local data.
* [Not shown] the ability to search, create new, and modify existing references should be able to be incorporated into editing workflows such as Citoid (see [[#Principles]] below)
{{-}}

Many other undescribed and unforeseen use-cases, metadata fields, and possibilities are certain to exist. Please describe them [[Talk:WikiCite/Shared Citations|on the talkpage]]!

====Scale====
With regard to the '''expected scale''' of the Shared Citations database: estimates vary greatly of the potential "total" number of de-duplicated references which exist across all Wikimedia projects and have the potential to be turned into Shared Citation records. A 2020 dataset extracted 29m references from English Wikipedia "to books, journal articles or Web contents",<ref>https://arxiv.org/abs/2007.07022</ref> while the Internet Archive tracks 23m archive-URLs across 46 Wikipedias.<ref>https://tools-static.wmflabs.org/botwikiawk/dashboard.html</ref> These datapoints indicate that the scale should be in the same order of magnitude as Wikidata itself, which currently hosts 90m items. Moreover, these datasets overlap, and neither includes Wikidata's references in scope. Being able to know just how many separate references exist across Wikimedia projects would be a benefit of the Shared Citations project itself.

=== Relationship to Movement Strategy ===
'''[[Strategy/Wikimedia movement/2018-20|Knowledge Equity]]'''

Real time visibility into our citation graph allow us to help marginalized languages, communities and subject specialists to curate their reliable sources for easy reuse. Also, it will dramatically reduce the citation management workload, especially for smaller communities. The challenge is: How might we identify citation gaps or imbalances, while not supercharging existing inequities?

* “This will help us achieve epistemological decolonisation” <small>– [[User:Joalpe|João Peschanski]]</small>
* “If libraries could look at global Wikimedia citations, it would help break a self-reinforcing cycle of certain sources’ popularity in library holdings” <small>– [[User:Phoebe|Phoebe Ayers]]</small>
* “Standardized templates and references benefit products designed for emerging markets, which need high interoperability of content formfactor, language, and projects.” <small>– [[User:Runab WMF|Runa Bhattacharjee]]</small>
* “Having systematic insight into where our knowledge comes from will help us to diagnose what kinds of sources, languages, voices are missing.” <small>– [[User:BVershbow (WMF)|Ben Vershbow]]</small>

'''[[Strategy/Wikimedia movement/2018-20|Knowledge as a Service]]'''

Shared Citations would underpin the reference ecosystem inside and around Wikimedia by making relatively raw data into semantic knowledge. The challenge is: How might reusers take advantage of a language-agnostic citation graph?

* “Commons makes it easy to use the same image on different wikis. But to copy a citation is very hard. Everything is manual and slow.” <small>– [[User:Aaharoni-WMF|Amir Aharoni]]</small>
* “Abstract Wikipedia articles will be far more useful if references are formatted from structured data instead of plaintext.” <small>– [[User:DVrandecic (WMF)|Denny Vrandečić]]</small>
* “Imagine being able to recommend useful footnotes to editors, readers.” <small>– [[User:Samwalton9 (WMF)|Sam Walton]]</small>
* “This adds integrity to our citations - “a fortified citation layer.” <small>– [[User:CAlbon (WMF)|Chris Albon]]</small>
'''[[Strategy/Wikimedia movement/2018-20/Transition/List of Initiatives|Individual strategic initiatives]]'''

1: Systematic approach to improve satisfaction and productivity [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Increase the Sustainability of Our Movement|Increase the Sustainability of Our Movement]]]

9: Community engagement around product design and UX [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Improve User Experience|Improve User Experience]]]

11: Resources for newcomers [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Improve User Experience|Improve User Experience]]]

14: Cross-project tool development and reuse [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Improve User Experience|Improve User Experience]]]

29: Enhance communication and collaboration capacity with partners and collaborators [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Coordinate Across Stakeholders|Coordinate Across Stakeholders]]]

36: Misinformation [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Identify Topics for Impact|Identify Topics for Impact]]]

37: Bridging content gaps [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Identify Topics for Impact|Identify Topics for Impact]]]

38: Content initiatives in underrepresented communities [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Identify Topics for Impact|Identify Topics for Impact]]]

40: Policies for experimentation with projects for knowledge equity [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Innovate in Free Knowledge|Innovate in Free Knowledge]]]

41: Continuous experimentation, technology, and partnerships for content, formats, and devices [<nowiki/>[[Special:MyLanguage/Strategy/Wikimedia movement/2018-20/Recommendations/Innovate in Free Knowledge|Innovate in Free Knowledge]]]

=== Use cases ===
{| class="wikitable"
|'''Knowledge creators'''
| rowspan="5" |
|'''Knowledge users'''
|-
| rowspan="2" |As a '''Wikimedian editor''', I would like to

* Quickly and easily add references to my article by reusing references from another language Wikipedia
* Benefit from the formatting done by others, so I can spend my time on research and writing, not on templates
* Train new users to add footnotes in one session, in a way they can continue without intense support
* Create ‘redlists’ for Wikidata of authors and publications which are frequently cited but don’t have a Wikidata item
* Have my work on disambiguating authors on Wikidata cascade through to their references on other Wikiprojects
|As a '''reader''' of Wikimedia projects, I would like to
* Understand if I can trust the citation I am reading
* Be suggested other topics in Wikipedia which also reference this same author or book
* See dictionary definitions which prioritise usage examples published in my country’s vernacular
* Generate a list of primary, or newspaper, or local sources used on this topic, for my highschool homework
|-
|As a '''library''', I would like to
* Track that Wikimedia external links to our collection from Wikimedia are well maintained
* Notice which books on our key subjects are cited and ensure our library has holdings
|-
|As a '''content patroller''', I would like to
* Tag all citations to an instance of disinformation or misinformation or a retracted publication across all projects
* See, when someone is adding the same link across many different projects in quick succession, and revert
* Identify and track any citations to [[w:en:Predatory publishing|predatory journals]]

*
|As a '''technology company''', I would like to
* Be able to answer the question “says who?” when a customer asks me to verify a fact just given them
* Train my algorithm to show more reliable sources for languages and topics where I have limited other data
|-
|As a '''professional writer''', I would like to
* Have academic ‘impact factor’ reports include Wikipedia citations to my scholarly work<ref>https://arxiv.org/pdf/2010.03083.pdf</ref>
* Check when Wikidata is referencing my work to ensure its findings are accurately represented
* Be notified when a Wikipedia article cites my journalism and be able to share it on social media
|
As a '''researcher''', I would like to
* Be able to extract parts of the citation corpus and analyse it, without massive pre-processing
* Know how many references are behind paywalls, how much do they cost, and if there are alternatives
* See how many references are ''about'' a language, culture, or place but were published from outside it.
*Assess the gender-ratio of authors cited in any given language or topic area, and changes over time.
|}
By way of illustration, the answers to the following questions could be useful to any or all of the above use-case groups. We currently lack the ability to answer basic questions about our own citation corpus without heavy one-time research investments. Questions such as:
* How many times is the ''New York Times'' cited as a source across all Wikimedia projects? Is its newer content cited more frequently than older content, and in which languages?
* Which Wikipedia articles in all languages reference a source in Russian, that the Russian community has flagged as unreliable?
* How many sources in languages other than Vietnamese are cited in Vietnamese Wikipedia? Which sources in Vietnamese are cited by a Wikimedia project, but not in Vietnamese Wikipedia itself?
* How often are works by Naomi Klein used as references? Which chapters, of which editions, of which books, are her most cited?
* Which articles exclusively cite paywalled scholarly articles, or articles which have been since retracted?
*'''''Other?''' <Add more here>''
Without the ability to answer these kinds of questions, it is difficult to ensure accuracy, consistency, and currency of our citation corpus. It is also near impossible to investigate our citation corpus for biases.

== Principles ==
''[[Talk:{{PAGENAME}}#Principles|Comment on this section]]''
=== Database ===
Combined, these principles are what makes the Shared Citations database a "service" project and not a new "sister" project.
# '''Pragmatic scope.''' Records in the citation database must have been used as a reference for a statement in any Wikimedia project page. It is ''not'' a place to compile completed sets of citation corpora (also known as "stamp collecting"<ref>https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7077981/</ref>) or an attempt at a universal a [[d:Wikidata:WikiCite/Roadmap#The%20%E2%80%9Cbibliographic%20commons%E2%80%9D|"bibliographic commons"]]. Its existence makes no impact upon Wikidata's own discussions of scope [see also [[#Relationship to Wikidata]]].
#'''Create upon use.''' Citation records are created by editors, at the moment that they are being used for a reference on a Wikimedia project. The citation database is not pre-populated with records that are not [yet] used as references in Wikimedia project page. There is ''no'' "create new citation record" workflow in the Shared Citation database itself – This is in direct contrast to other Wikimedia projects (e.g. Wikidata's "create new item" or Wikimedia Commons' "upload file" workflows). In effect, new records are created by being "pushed" to the Shared Citations database from one of the sister projects.
# '''Non-deprecation.''' Existing referencing systems remain. The existence of the Shared Citations database being "enabled" to be used on a wiki does not prejudice the continued use and addition, removal, or modification of ‘traditional’ references. For example, an editor can add two new references to a Wikivoyage page—one from Shared Citation database, and one in the 'traditional' way. Policy and technology allows for both to coexist on the same page. Equally, if another editor wishes to convert them to both be of either style, they may do so – in accordance with all editorial and behavioural policies on that Wiki. This is analogous to how each Wiki determines its own [[Non-free content|multimedia "local uploads" policy]]. The many edge-cases of what can be used as a reference means many might not even be possible to make into Shared Citation records – this diversity of reference content should be encouraged not stifled.
# '''Enabled upon readiness.''' Access to the Shared Citations database from a wiki should not be enabled before that wiki's workflows, policies, and templates are generally ready to use the new system. Access to the shared citation database is not enabled before a community has received reasonable support and time to be ready to benefit from and manage it. This means that enabling the system in a Wiki would ''not'' be subject to a fixed rollout-timeline, but rather to whether that community felt prepared. Nonetheless, this principle should ''not'' be construed to mean that all templates need to be converted, or all local administrators have to agree, before the system can be enabled. Because of the "non-deprecation" principle, no existing workflows would break when the new system is enabled.
# '''Style independence.''' Local wikis determine the display format of a reference for the reader. [See also: the en.wp editorial guideline [[w:Wikipedia:Citing sources#Variation%20in%20citation%20methods|"variation in citation methods"]] (CITEVAR)] Shared citations provide the ''content'' of a reference but do not determine the ''form'', which can be structured by local tools and templates. For example, a shared citation of the type "scholarly article" might have a default display format for author names as "Last, First", but it must be ''possible'' to programatically alter it to be displayed as "F. Last". This display format could be set by: an adjustable parameter in each individual reference, a template covering a whole page, the fixed formatting of the chosen template, standardised across the entire wiki, or even as a user preference (or any combination of these, at the discretion of the local community).
# '''Editorial independence.''' Local wikis determine their content standards. [See also: the en.wp editorial guideline [[w:wp:RS|"reliable sources"]] and [[w:Wikipedia:Reliable sources/Perennial sources|"perennial sources"]]]. The existence of a shared citation in the database does not prejudice another project’s policies, and vice versa. For example, a shared citation exists, having been created from a reference in the Romulan Wikipedia which is using a website that the Vulcan Wikipedia has 'banned' as an unreliable source. The Vulcan Wikipedia is under no obligation to use the footnote merely because it is used by the Romulans, but equally the Romulans are not required to delete the citation merely because the Vulcans have banned it.

Finally, the general principles listed in “[[mw:Principles|MediaWiki:Principles]]” apply.

=== Cross-wiki integration ===
Community feedback from [[#Precedents & related projects]] indicate two broad areas needing improvement before structured data integration efforts across wikis would be more widely embraced. These are exemplified in the template-deletion debates on English Wikipedia for: [[:en:Template_talk:Cite_doi#RfC:_Should_cite_doi_template_be_deprecated?|"Cite DoI" (2015)]] and [[:en:Wikipedia:Templates_for_discussion/Log/2017_September_15#Template:Cite_Q|"Cite Q" (2017)]]

In ''all editing environments,'' editors must be able to:
# '''Monitor changes''' which affect how content is displayed to readers ''here'', even when it was edited over ''there''. This monitoring integration must be '''Granular''', '''Arbitrary''', and '''Cascading'''.
#*'''Granular''' means that watchlist must be able to show every change that affects what is shown to a reader of that page—no more, no less. This will avoid watchlists being "flooded" with irrelevant changes. Also applying this principle to the Page History might be possible, though it is a separate engineering task.
#*'''Arbitrary''' means the citation information being changed and displayed on the client wiki (e.g. Wikipedia) might come from any Wikidata item referenced in the citation.
#*And '''Cascading''' means a dependency tracking system must propagate notifications through any and all affected items across sites (Wikipedia article, Shared Citation record, Wikidata item), regardless of the origin of the change [[phab:T253026|T253026]].
# '''Access the content''' which will be shown to readers ''here,'' even though it is hosted over ''there.'' This access takes three forms – to '''jump to''' to where the citation is stored, to '''inspect''' the content in situ, to '''edit''' the citation in situ. Given that references are an important part of any Wikimedia page's content, even when the text content of a reference is actually being hosted in a separate database, an editor of a page must be able to easily view [and text-search] all the content which will be displayed in the saved page whilst in editing mode. The nature of that access would differ depending on the editing environment [including mobile and screen-readers] and could be implemented in various ways. Nonetheless, in all editing environments, it must be made easy to 'jump' directly to where the reference's content is stored in the shared citation database, where it can be edited. Furthermore, and depending on the technical capabilities of the editing environment, an editor should be able to edit a 'shared citation' reference (including adding new ones) without leaving the page.
Finally, the general principles listed in "[[w:User:Risker/Risker's checklist for content-creation extensions|Risker's checklist for content-creation extensions]]" apply.

==MediaWiki Development==
''[[Talk:{{PAGENAME}}#MediaWiki Development|Comment on this section]]''

These two specific areas of community feedback relating to cross-wiki integration require MediaWiki development to improve the cross-wiki integration of ''Monitoring,'' and also the cross-wiki integration of ''Editing''. The status quo can be understood as incomplete ecosystem integration. The "minimum viable product" needs of this work are:

=== Monitoring ===
Relevant subscribed watchlists will:
* '''update''' when a change to any entry '''in the citations database''' affects how a page will display to a reader. e.g. The ISBN of a Shared Citation record is changed
* '''update''' when any change '''to a Wikidata item''' which is used in a citation database entry, affects how a page will display to a reader. e.g. the label of an author is changed in Wikidata in the same language as where the Shared Citation record is used in Wikipedia.
* '''update''' when an editor changes information in the same shared citation in use on a page in another Wikimedia project, when it affects how a page will display to a reader the watchlists and recent changes relating to ''both'' articles is updated. e.g. When an editor on Klingon Wikipedia adds a publication date to a reference which is stored a shared citation that is also used in an article on the Vulcan Wikipedia, the watchlists of people who monitor either article are updated.
* '''''not'' update''' when any change to the above would have no affect on how a page will display to a reader. e.g. 1: if a new field/property is added to the citation record, but that field is not displayed in the reference. e.g. 2: if a label is changed but in another language
* '''indicate''' to the user the origin and nature of the change for easy tracking. e.g. including edit summary, #tags or equivalent flags, the username, the sisterproject where the edit originated, and that the change was propagated "via shared citations database".
Work on this issue, or close variation on it, is already underway within Wikidata and would need to be coordinated so as to not duplicate effort [[phab:T90435|T90435]], [[phab:T191831|T191831]]. This monitoring functionality, once built, should be applicable to other cross-wiki use cases. e.g. 1: If a Wikimedia Commons file is deleted or replaced [[phab:T91192|[T91192]]].

Above and beyond ''watchlist'' monitoring, these updates might also be applicable to the relevant ''page history''. While they serve a similar monitoring purpose, page history is constructed independently of watchlists and would require separate engineering effort. Further research is required.

===Editing===
[[File:Citoid results in VisualEditor Screen Shot 2015-04-02.png|thumb|A screenshot of the [[mw:citoid|Citoid]] system in Visual Editor. As far as possible, editor-interaction with a "shared citation" within their wikis should utilise existing services and workflows.]]
The ''minimum'' viable product (MVP) for actions across the various editing environments should be as follows. The user interface and workflow of each action would be dependent on the editing environment.

'''All editing environments'''

[Including in the [[mw:Extension:WikiEditor|2010 Wikitext editor]]]

* '''Inspect''' an existing citation. View the content of what is shown to the reader and easily access the page where that data is stored and is editable. Implementations could include popup on click, appear on hover, dropdown from the toolbar, display as a group below the editable area, etc.
* '''Jump to''' the Shared Citation record in the database. Simply and easily access the page in the shared citations database where the specific citation is actually hosted, in order to edit there – without interrupting the original editing workflow. Implementations could include a link to open a new tab, a popup...
'''Mobile editor'''

All of the above, and also:

*'''Find'''. When using the browser's inbuilt text-search system (ctrl+F) while in editing model, be able to search for text strings which would appear to the reader of the page (e.g. "Hugo, Victor") even though that sting is hosted on the Shared Citation database and only the Shared Citation record's ID number is embedded in the article's wikitext.
* '''Create'''
** New. This ought to be integrated with the current "create a new reference" [[mw:citoid|Citoid]] workflow. Adding all the relevant metadata to a newly created record in the Shared Citations database. Requires searching the database before creating a new record to check that it doesn't already exist. This is expected to be a ''primary means'' by which new references are created in the shared citation database and is therefore a critical workflow.
** Existing. Creating a new reference in the page to something which ''already'' has a citation record in the Shared Citations database. Essentially a widget that searches that database for the URL/ISBN/DoI/etc of the intended source, selecting the correct response and inserting that Shared Citation database ID directly.
*'''Reuse'''
**Repeat. Making another reference in the same page to something which is already referenced on that page. Essentially equivalent to existing workflow that utilises <refname>, but working on Shared Citation references.
**New subsection. To be able to repeat an existing reference but to a different subsection - e.g. edition, page, chapter...
* '''Modify''' existing reference. Equivalent to existing workflow, but also working on Shared Citation references.
** Connect citation record fields about concepts to equivalent items in Wikidata (e.g. author, publisher, main subject), when they exist. This workflow also applies equally to the aforementioned "create" workflows. [See examples in the wireframes in the [[#Shared Citations]] section above].
'''[[mw:Extension:VisualEditor|Visual Editor]] & [[mw:2017 wikitext editor|Source Editor]]'''

All of the above, and also:
*'''Convert''' an existing reference to a Shared Citations reference. A wholly new workflow, which allows a user to "push" an existing "traditional" reference's content it to the Shared Citations database, to create a new record over there, and then bring that new record's ID back to the page to be saved. This is expected to be a ''primary means'' by which new references are created in the shared citation database and is therefore a critical workflow.
'''Read mode''' [optional]

All of the above. As [[mw:Wikidata Bridge|Wikidata Bridge]] is demonstrating that it is ''also'' possible to consider the "read" mode as an editing environment in its own right – where users can click upon an icon inline and, via a popup widget, edit structured data fields. This occurs without needing to click the "edit" button at all. This editing mode ''could'' also be implemented and ''could'' could be used as a method to achieve some of the features described above if it is not feasible to achieve in a particular editing environment (notably with the 2010 Editor).

'''WikiBase'''

All of the above. Wikidata, among all sister projects, uses a unique editing environment – one that does not group the fields of a reference together in a citation template. Furthermore, Citoid is not available in Wikidata (yet) [[phab:T199197|T199197]]. As mentioned in [[#Examples of the status quo]] above, reference fields in Wikidata are edited independently even when two references' information is identical, on the same property, on the same item. A unique UX would need to be developed for the creation of new Shared Citation records within Wikidata, for their visualisation by readers, and for the conversion of existing references to Shared Citations.

'''Bots & tools'''

The existence of means of mass-editing in Wikimedia projects by community-designed and operated bots must be accounted for and supported as best as possible. Notably, supporting new workflows of '''automated- and semi-automated conversion''' of existing references (by community owned/operated tools and bots), to move the metadata of references to the Shared Citations database and replacing it with a Shared Citation record ID [in accordance with local bot-flag editing permissions]. Equally, linking or annotating a Shared Citation record with its associated Wikidata items (including authors, publisher, main subject etc.) is another candidate for automated or semiautomated tools – as demonstrated by the existence of several bots and tools already developed by the community for this purpose in Wikidata.

== Considerations ==
''[[Talk:{{PAGENAME}}#Considerations|Comment on this section]]''

=== Workflows ===
The following topics are a non-exhaustive list of workflows and processes in the Shared Citations database which need to be created and owned by the community to ensure the operation of a new database which hosts content which serves all Wikimedia projects.

* '''Administrator,''' '''Bot''' and other requests for permission process. Equivalent to all other wiki projects [See also Wikidata's various "[[d:Wikidata:Requests for permissions|Request for permission]]" processes]
*'''Accessibility''' ''A11y.'' Need to ensure that screenreader software can still access the content of a Shared Citation reference in an article page. Would need to ensure that it is ''at least'' as accessible as current locally-hosted [[w:en:Category:Specific-source templates|Specific source templates]]. Other potential future software development work to help build a shared template schema will facilitate applying high accessibility standards across all wikis.
*'''Blocking''', banning, oversighting and related moderation workflows, policies, and associated user-rights. [See also Wikidata's [[d:Wikidata:User access levels|"User access levels"]]]
*'''Creation'''. All new records would be "pushed" from the sister projects, either through newly created references or converting of existing references, via the [[WikiCite/Shared Citations#Editing|#Editing environments]] describe above. There would be no "create new record" workflow – either manually or mass-edit – in the Shared Citations database itself, as described in the [[WikiCite/Shared Citations#Database|#Principles]] section.
*'''Deletion''' and under what circumstances. If a record is being used in any Wikimedia project that would make it automatically valid for retention. But what happens when a citation is ''no longer'' used in any Wikimedia page? See also "Spam" in the [[WikiCite/Shared Citations#Open%20questions|#Open questions]], below.
*'''Editorial dispute''' management. Given that a Shared Citation record can be used simultaneously on several wikis, and can also be edited ''from within'' those wikis, any changes will propagate back out to all the places where the citation is used (and with associated updates to local watchlists). Editorial disagreements would be fewer – since the scope of the database is purely the citation metadata, not the facts in the work itself – but not entirely absent. Wikimedians will still need to be able to easily identify the talkpage (or equivalent) of where to discuss the best way to structure that reference.
*'''Merging.''' Presumably a workflow that can only happen when working in the database itself (not an action performable while editing an individual reference from within a sister project page. Equivalent workflow and outcome to the process of [[d:Help:Merge|merging Wikidata items]] - requiring redirecting the duplicate item number (and never reusing it), concatenating the metadata. Gadgets and tools can be built to facilitate the process. Bots on wikis could have redirected item cleanup as a task.
* '''Property''' creation/deletion proposal and approval process; and associated user rights [See also Wikidata's [[d:Wikidata:Property creators|"Property creator"]] user right]
* '''Identify''' commonly reused strings (authors, publishers) to create items-for-creation worklists for Wikidata. [See also English Wikipedia's [[w:Category:WikiProjects relevant for countering systemic bias|"lists of redlinks" projects to counter systemic-bias]]]
*'''Protecting''' or semi-protecting records, or individual fields within them which have high usage or are easily misused. [See also Wikidata's "Highly used items" [[d:Wikidata:Page protection policy|page protection policy]]].
*'''Schemas''' for defining the relevant and necessary properties (and ontology) for different types of sources which can be used as citation records. E.g. All types of sources should have some kind of "publisher" field, but the "ISBN" field is only relevant to some types of sources. [See also Wikidata's [[d:Wikidata:WikiProject Schemas|Project Schemas/Shape Expressions]] project]
*''Other? <Add more here>''

=== Relationship to Wikidata ===
In Wikidata there is a vibrant community, extensive data modelling, and a corpus of existing citation content (for example, Wikidata's [[d:Wikidata:WikiProject Source MetaData|"WikiProject Source MetaData"]] and [[WikiCite]] more generally). It has been often suggested that Wikidata should include within its scope either a universal citation database, or a database of all Wikimedia citations. [See also the [[d:Wikidata:WikiCite/Roadmap|WikiCite "Roadmap" discussions]] and the [[#Background]] section, above] However, as "Shared Citations" is proposed to ''also'' support the references workflow in Wikidata, it is more accurately seen as a service project which sits "behind" and "among" the Wikimedia sister project. The Shared Citations database is different from, and non-competing with, Wikidata in the following ways:

* '''Scale''': A separate database means that all Wikimedia citations can “fit”. E.g. the 10s of millions of citations to specific URLs.
* '''Service''': By serving all Wikimedia projects, Wikidata itself can equally be a beneficiary of the shared citations for references used in its own statements.
* '''Scope''' #1: Restricting to only Wikimedia citations ensures the ontology remains practical.
* '''Scope''' #2: Restricting to only creation-upon-need ensures the community understands the difference from WD.
*'''Sovereignty''': Wikidata and the Shared Citations database would be editorially independent. Some content overlap, but would be overwhelmingly limited to individual scholarly journal articles, some book editions. WD does not often have items about URLs, newspaper articles etc. Content policies would nonetheless need to adapt.
{| class="wikitable"
|+Comparison of Shared Citation and Wikidata scope and content
| style="vertical-align: top" width="50%" |'''Shared Citations database'''
| style="vertical-align: top" width="50%" |'''Wikidata'''
|-
| style="vertical-align: top" |'''Service''' project
| style="vertical-align: top" |'''Sister''' project
|-
| style="vertical-align: top" |'''Records''' about specific individual publications:

Scholarly publications, URLs, editions of books, newspaper articles, archival records...
| style="vertical-align: top" |'''Items''' about concepts:

Authors, publishers, newspapers, websites, main subjects....
|-
| style="vertical-align: top" |Only that which is cited as a reference in a Wikimedia project (including Wikidata).

Only created upon their being used in a Wikimedia project, individually or semi-automated.
| style="vertical-align: top" |Any works.

Created in advance, en masse, for any use case.
|-
| style="vertical-align: top" |Example Shared Citation record types:
* ''Metamorphoses''. Ovid. Translated by A. D. Melville; introduction and notes by E. J. Kenney.<br> Oxford: Oxford University Press. 2008. <nowiki>ISBN 978-0-19-953737-2</nowiki>.
* <nowiki>https://www.theguardian.com/technology/2018/mar/13/youtube-wikipedia-flag-conspiracy</nowiki>
* Mérimée: IA68002588
| style="vertical-align: top" |Examples Wikidata Items:
* Metamorphoses ([[d:Q184742|Q184742]])<br>

* The Guardian ([[d:Q11148|Q11148]])
* Château de Morimont ([[d:Q947416|Q947416]])
|-
| style="vertical-align: top" |Estimated size: ~50-100m records
| style="vertical-align: top" |Current size: ~90m items
|}
[[File:Wikidata statistics of publications and citations for WikiCite.png|thumb|Publications and citations in Wikidata over time, from [http://wikicite.org/statistics.html Wikicite.org/statistics] There is an important relationship between the Shared Citations and Wikidata.]]
Due to its unique data format among the Wikimedia sister projects, the interaction of this new references format with the [[d:Wikidata:SPARQL query service|Wikidata Query Service]] would need to be considered so the content could still be queried, perhaps with federated search.

Unlike on the other Wikimedia sister projects, Wikidata references are ''all'' structured data and are ''all'' in the same format, and there are ''no'' reference templates. It is therefore ''theoretically'' ''possible'' that all Wikidata references could be converted to becoming Shared Citation records. It would then be possible to enforce that all new references be made in the new format and the old format deprecated. However, while technically possible, these are both editorial decisions which would rest entirely with the Wikidata community as per [[#Principles]], above.

=== Integration with other Wikimedia software ===
The following is a ''non-exhaustive'' list of other pieces of software in the Wikimedia ecosystem with which Shared Citations would need to be either integrated with, or at the very least, be aware of its impact upon them.

==== WMF-developed ====
*'''[[mw:API:Main page|APIs]]''' and third party reuse features (such as the [https://stream.wikimedia.org/?doc#/ EventStream for "page-links-change"]) would need to be aware of new workflows for the insertion and deletion of references in Wikimedia projects. The dataset (live-changes, or archive-dump) could be particularly useful for academic research purposes.
*[[mw:Extension:Cite|'''Cite extension''']] – the system which manages the <nowiki><ref></nowiki> and <nowiki><references /></nowiki> tags.
*[[mw:Citoid|'''Citoid''']]. The primary tool for the creation and modification of references in Wikis in the Visual Editor and Source editor modes. As per the non-deprecation [[WikiCite/Shared Citations#Principles|#Principle]] the capability to insert traditional references should be retained. As described above in the [[#Editing]] section, integrating Shared Citations with Citoid would allow the most seamless user experience. For example, creation of a new "shared citation" in Citoid would require the user to paste a URL, DOI, or ISBN into the wizard (as usual) but instead of going directly to the web to look for information to scrape, Citoid would first check the Shared Citations database to see if that reference has already been used elsewhere and therefore is in the database. If so, it would collect the citation ID number and insert that into the Wiki page's code. If that record did not exist in the Shared Citation database yet, Citoid would create it, with the information that it would normally have saved directly into the wiki page, and then bring the Citation ID back and save.
[[File:Cx-screenshot-aug-2017.png|thumb|The [[mw:Content translation|ContentTranslation tool]]]]
* [[mw:Content translation|'''ContentTranslation''']] (CX). An important tool for creating new Wikipedia articles in smaller languages and a common workflow for training events. Currently, the tool has to "guess" what the relevant equivalent citation template is when converting from one language to the other – resulting in lost data (and lower data quality) in the conversion process. If both source and target wikis have Shared Citations enabled it will become a trivial process.
*[[The Wikipedia Library|'''The Wikipedia Library''']]. TWL allows Wikimedians to have privileged access to otherwise close-access academic databases. The existence of Shared Citations would permit new features such as "Recommended citations" (based on equivalent articles in other languages) and a field for proxied URL access from the database (see wireframe examples above).
*[[Visual Editor|'''Visual Editor''']] – the most feature-rich editing environment and the assumed primary means of creating and editing Shared Citation references.
*[[mw:Wikidata Bridge|'''Wikidata Bridge''']] – currently under development by Wikimedia Deutschland. A project to enable Wikidata editing from within Wikipedia infoboxes.
*''Other? <Add more here>''

==== Community-developed ====
*'''Bots''' (e.g. [[w:User:Citation bot|User:Citation bot]]) which undertake pre-approved, autonomous, editing "cleaning" processes, often relating to standardising template usage.
*[[w:Template:Cite Q|'''Cite Q''']]. A citation template that enables relevant Wikidata items to be used as references in Wikipedias in locally defined formats.
*'''Citation Styles''' (e.g. [[w:wp:CS1|CS1]]). Not software per se, but important code-consistency efforts to ensure that a Shared Citation record renders to the reader appropriately.
*[[mw:Global templates|'''Global Templates''']] – current proposal to centralise the creation and hosting of templates used across many wikis.
*'''Tools''' Various semi-automated editing aid tools which focus on improving or adding references in Wikimedia projects e.g. [[AutoWikiBrowser]] and many others listed at [[w:Help:Citation tools|English Wikipedia]]; [https://hay.toolforge.org/directory/ Hay's directory]. A new database focusing on structured data ''will'' cause new tools to be developed, and this must be accounted for and supported. It can be assumed that tools for the semi-automated "conversion" of many 'traditional' references to Shared Citations records will become a critical workflow for the growth of the Shared Citations corpus and wider uptake on sister projects.
*[[w:User:Cacycle/wikEd|'''WikEd''']]. A text editor extension providing advanced editing tools (including content-folding of citations) for the [[mw:Extension:WikiEditor|2010 Wikitext editor]].
* [[mw:Extension:Semantic_Cite|'''Semantic Cite''']] is a MediaWiki extension providing a simple way of organizing citation resources with the help of semantic annotations.
*''Other? <Add more here>''

=== Open questions ===
The following is a ''non-exhaustive'' list of decisions that need to be taken by the community as the project gets built.

* '''Spam''' management. A service that centrally hosts content visible to reusers (e.g. search engines) creates a new vector for spam link promotion. Centralising citations allows easier identification and followup of poor quality links from common domains. Being a "service project" (rather than a public-facing "sister project") there is minimal direct audience and hopefully reduced spammer motivation and the use of "Nofollow" tags decreases SEO spam. Nonetheless, spammers will undoubtedly find innovative ways to stress the system. A potential way to mitigate the risk would be to have a "speedy delete" policy for newly created Shared Citation database record where the associated and sole reference on the originating wiki was itself removed within a short period of time.
*Cross-wiki "[[w:Wikipedia:Reliable sources/Perennial sources|'''Perennial sources''']]" management. Smaller language communities often don't have the community scale for local moderation projects of external source quality so centralising the reference management would logically lead towards centralised monitoring of source quality. What kinds of properties or processes might need to be invented to support that (without overriding local wiki editorial autonomy)? For example, some sources may be allowed only for particular kinds of topics (e.g. sport but not politics), some wikis might restrict them to being added by users with extended permissions, some may be banned on particular wikis, some may be banned for all wikis....
*To which '''namespaces''' on the sister project wikis should the Shared Citation system be associated? Any reference—even on policy pages, talkpages? userpages? Related to the aforementioned spam management, one option is to only create Shared Citation records when the reference is used in the ''main'' namespace of a wiki (to avoid the potential of a spammer creating a user-subpage filled with external URLs simply to create them in the database). However, this solution would hinder the creation of legitimate userspace drafts.
*The relationship of the Shared Citation database's '''properties''' to those in Wikidata. Is the localisation ''L10n'' of property names for all languages is most appropriately done in Wikidata (and then import the properties via "federation"), or should it be done in the Shared Citations database itself? It would benefit from shared effort to use Wikidata's properties, but it would also mean that some properties ''only'' needed for Shared Citations' use case would be created in Wikidata: Would the WD community accept that?
*Referencing '''different subsections''' (e.g. different pages, chapters, editions) of the same citation in a single article. How should the system handle different references in a page which are to the same Shared Citations record ''but different subsections''. The Shared Citation record ought to be able to group all references to different subsections onto the one record (see wireframe examples above). How this would integrate with existing editor behaviour and reader expectations would need careful consideration to ensure that use cases and nuance are not lost (see the "reuse" workflow described above).
*'''Re-using the same reference''' in a page. The functionality of the <nowiki><ref name></nowiki> feature – which allows a single reference to be called upon multiple times in one page – would need to be replicated. Equally, the ability to refer to a different page of a reference already in use in that page (see the "Reuse" workflow described above).
*Relationship to '''Wikisource''' pages. Wikisource's transcribed documents rarely have citations ''in'' them, and when they do linking to the Shared Citations record should not alter the esoteric way that citation is displayed (as it should be an accurate transcription). Moreover, these transcribed documents often ''are'' the document being used in a reference elsewhere. Each Wikisource document should have a matching Wikidata item but it should ''not'' automatically have a Shared Citations database record until that document is being used for a reference in a Wikimedia project. When it is, that Shared Citation reference in a Wikipedia article to a document which also exists in Wikisource should be connected together seamlessly. What is the best way to do that - perhaps with a dedicated "equivalent"?
*Relationship to '''Wikidata items about works''' which are also used for Wikimedia references. There are a large number of Wikidata items about specific works which are ''also'' things that have been used in Wikimedia projects, notably scholarly journal articles. These would now exist ''twice'': once in Wikidata as an item in their own right, and once in the Shared Citations database as something which has been referenced from [for example] a Wikipedia article. There would need to be a community consensus built as to how these two interact with each other. Tools such as ''Cite Q'' would need to be adapted to support that new consensus.
*'''Integration in wiki syntax'''. Currently, all references in MediaWiki use the [[mw:HTML element|XML-like element <nowiki><ref></nowiki>]], provided by the Cite extension to denote a reference. In order to be able to differentiate Shared Citations and not 'overload' [the editor ''and'' the software] from that without any interruption to the existing system, it might be necessary to use a new piece of syntax (perhaps <nowiki><cite> or {{#cite}}</nowiki> ) to invoke the new functionality. The specific technical implementation, and implications for accessibility, right-to-left (RTL) languages, and other localisation considerations need to be explored.
*'''Database Dumps'''. When the data in the references are hosted separately, can a complete database dump of a wiki still be generated which includes the references. Or, can a dump of the Shared Citations database be provided which provides the relevant information? This question equally applies to where Wikidata is generating significant quantities of content in another wiki.
*Mismatched page/item '''protection state'''. How to deal with circumstances where a Shared Citation record is used in multiple pages (potentially across multiple wikis), but where some of those pages are [[Help:Protection|protected]] from general editing. For example, if an anonymous editor edits a citation on a page in the Klingon Wikipedia, that change would be saved on the Shared Citation database and propagated out to all other locations where the same citation is used. However, if one of those uses is on a Vulcan Wikipedia article which is fully-protected, how should that change be handled? This is an equivalent issue to Wikidata facts being embedded in Wikipedias.
*'''Multiple versions of the same work''' Most journal articles likely to be cited exist in both print or electronic format; most books, in several editions. Existing WP references are highly variable in which they cite; even some standard "reliable" reference sources like OCLC are inconsistent and sometimes incorrect. Do we accept references however cited, or attempt to verify and unify them?
*'''''Other?''' <Add more here>''

== Partners==
=== Internet Archive ===
[[File:InternetArchiveBot Dashboard.png|thumb|The InternetArchiveBot's current [https://tools-static.wmflabs.org/botwikiawk/dashboard.html web archive statistics] page; A project which could be greatly simplified if it could integrate with a single Shared Citations database.]]
{{Quote|text= For the better part of a decade the Internet Archive has been archiving the content of Web pages linked from Wikipedia Articles (and Web pages linked from those pages as well) in near-real-time. Millions of URLs/week. And, with the [[InternetArchiveBot]] we have helped rescued more than 14 million URLs that had been returning a 404 (page not found) by editing those broken links to point to Wayback Machine (and other Web archive) links. We have run InternetArchiveBot on more than 50 Wikipedia sites and are in the process of setting up the software to run on even more.}}

{{Quote|text=As part of our [https://www.wired.com/story/internet-archive-wikipedia-more-reliable/ Turn All References Blue] (TARB) project we recently started using InternetArchiveBot to help add links to digital versions of books referenced in Wikipedia articles. To date we have added more than 700,000 book links to 10 Wikipedia sites. As a demonstration of the commitment of the Internet Archive to this project, in 2019 one of our sister non-profits purchased the online book store [https://www.betterworldbooks.com/ Better World Books], allowing us to pull books cited in Wikipedia articles off conveyor belts, digitize them, and add links to them.}}

{{Quote|text=In the course of this work we have built databases of URLs, and book/academic paper citations, from more than 50 Wikipedia sites. We built, and maintain, those databases out of necessity, to power our broken link fixing, and links to books/papers, efforts. Here is [https://tools-static.wmflabs.org/botwikiawk/xcite/xcite.html an inventory of some of the citations templates we imported metadata from] (from just 2 Wikipedia sites) to help populate our databases. Our goal is simple… every link, and citation, in every Wikipedia article, in every Wikipedia site should be persistent, reliable and take the curious to (at least) a snippet of the cited work. Here is [https://tools-static.wmflabs.org/botwikiawk/dashboard.html an incomplete report] of our work to date. '''The Shared Citations Database proposal would be a godsend''' to help support the TARB project, help the Internet Archive acquire, digitize and link more works to citations and, in so doing, help make Wikipedia sites, and the Web, more useful and reliable.}}
::– [[User:Markjgraham hmb|Mark Graham]]. Director of [[w:Wayback Machine|Wayback Machine]] at Internet Archive

=== Scribe ===
[[File:Scribe logo.png|thumb|100 px|Scribe aims to support low-resource Wikipedia editors in creating new articles.]]
{{Quote|text=[[Scribe]] is a project to support low-resource Wikipedia editors in creating articles in their language. One of the most important components of the project is to suggest references to the editor, ideally in their language. To give the reader an insight into the quality of the reference, we opted to show them (among other things) how much the reference is used on Wikipedia already, in their language Wikipedia and in the topic area they are writing about, with a focus on online references. This information is currently extracted from Wikipedia dumps, but to be more flexible would need to be stored in a central place.}}
{{Quote|text=While creating the database for Scribe about online references, we found that there is a general need for a centralised place for references, to understand, for example, how much references are used across languages. We, therefore, opened a part of our dataset with an API: [https://misinfocon.com/scribes-reference-api-makes-credibility-more-attainable-6360824b47e4 Scribe's credibility API]. This API supports analysis of references and is available in 10 Wikipedia languages. But the fact that it needs to process the dumps limits its actuality, which the Shared Citations project could tackle.}}
::– [[User:Frimelle|Lucie-Aimée Kaffee]], [[Scribe]]

'''Other?''' <Do you represent another organisation which would like to consider itself a 'partner' of this project? Please add details here>

== Timeline ==
{| class="wikitable"
|+
''timeline estimate''
! rowspan="2" |Past
|2020
July–October
|Initial stakeholder interviews
|-
|November–December
|
* Initial proposal to WMF management
* Initial proposal publication on Meta
|-
!style="background:lightgrey"|Current
|style="background:lightgrey"|2021

Q1
|style="background:lightgrey"|'''"Pilot approval" phase'''

* WMF annual planning process, defining the resource requirements
* Architectural exploration with WMF Architecture Team
* Grantwriting
|-
! rowspan="4" |Future

''pending approval *''
|Q2
|
* WMF ramp-up (e.g. hiring)
* Researching "current state of citations" across Wikimedia

* Community consultation and designing

[if pilot approval phase is successful]
|-
|Q3-4
|'''"Design" phase'''
* Design research
* Engineering design and prototype
* Monitoring + Editing backend research
|-
|2022
Q1-2
|'''"Pilot" phase''' [if design phase is successful]
* Launch database
* Community building + properties
* Iteration on Monitoring + Editing integration
* First user actions in 1st round of supported wikis
|-
|Q3-4
|'''"Beta" phase''' [if Pilot phase is successful]
* Completed workflow support for 1st round wikis
* Enable on 2nd round of wikis
* Populating with content + support community tools...
|}
''The further into the future the proposal reaches, the timeline naturally becomes less clear/fixed.''

<nowiki>*</nowiki> The concept of "approval" for this complex project is very difficult to define. As this project would requires significant software development investment ''and also'' community involvement, approval would be required from both the WMF executive (through its [[Wikimedia Foundation Annual Plan|annual planning process]]) and volunteer editing community (perhaps through a [[Proposals for new projects|proposal for new projects]] RfC process?). However, both the editing community and Wikimedia Foundation executive would need to see that the proposal has received in-principle support by the other, and also neither would wish to feel that the other has made a decision without consulting them first. This "delicate dance" is why the early-2021 rows have parallel WMF/Community elements. The most likely scenario is a series of phases which each require a more formal approval from either WMF, Community, or both – These have been tentatively described in the above table as the "pilot approval", "design", "pilot" and "beta" phases. Furthermore, the software development described in [[WikiCite/Shared Citations#MediaWiki%20Development|#MediaWiki Development]] would be beneficial to many aspects of Wikimedia projects whether or not the Shared Citations database itself was created, meaning it could be worked upon independently of any approval process for creating a new citation management system (or enabling it for use on any individual sister project wiki).

=== Rollout & Metrics ===
This is a ''suggested'' order for rollout prioritisation while recalling that the [[WikiCite/Shared Citations#Principles|#principle of "enabled on readiness"]] means that rollout would follow the order of community demand (and therefore would not be a neat "all language editions of a sister project" in sequence).

The prioritisation of the rollout should be focusing on, 1) ensuring the diversity of the community engaging in the Shared Citations database is broad from the beginning (ensuring the culture of the project is not overwhelmed by one 'form' of knowledge management from the beginning), and 2) ensuring the corpus of the Shared Citations database grows to have a likely high overlap with needs of the subsequent groups.

'''Pilot''': [[incubator:Main_Page|'''Incubator''']] and/or [[Abstract Wikipedia|'''Abstract Wikipedia''']]. Single MediaWiki instance representing multiple language communities which are the smallest in the movement – ensuring a diversity of cultural contexts of references built in from the start. Highest need for technical simplification, lowest risk of negative hostile response to beta software.
#'''Wiktionaries''' & '''Wikiquotes'''. Community familiar with complex citation management and citation reuse. Diversity of citation types, template formats, and languages. Corpus of most oft-cited works. Built on MediaWiki.
#'''Wikidata.''' A large number of citations already in a consistent structured format. A single wiki with a multilingual and multicultural community, familiar with structured-data, properties etc. Necessary community discussion on how properties and content should be mapped to each other. Built on WikiBase which would require bespoke UI and workflows.
#'''Wikisources'''. Most active community entirely among “emerging communities” ensuring citation diversity built-in to the culture.
#'''Wikibooks''' & '''Wikiyoyage'''. Smaller projects which are closest in style to Wikipedias
# '''Wikipedias''' and other sister projects. Largest block of content – most benefit from the "network effect" of increased corpus size and community curation of the corpus. Largest variety of citation formats and edge cases.
Possible metrics and associated targets for determining "success" should focus on the '''number of individual editors using''' the system (and continuing to use); '''proportion of newly-created references''' being created in the new system on a wiki relative to 'traditional' style; the '''proportion of total references''' on a wiki using the new system; '''diversity of types of citations''' '''supported''' by the system; '''average number of reuses of a citation record''' (compared to an existing system baseline); and the '''number of Wikimedia communities''' widely/consistently using Shared Citations on their wiki. The metric of success should explicitly ''not'' include the speed at which rollout to new wikis occurs (this would encourage haste over readiness) ''nor'' total number of records in the Shared Citations database (which would encourage record-creation before the community is ready to support it).

== References ==
<references/>

== Endorsements ==
If you would like to list yourself as supporting this proposal, please sign your username below. If/when this project moves into the stage of resource-investigation for software development in the WMF and WMF annual planning, a [[Proposals for new projects|proposal for new projects]] listing would be published.<br>If you would like to provide substantive feedback, ask questions, or comment please use [[Talk:WikiCite/Shared Citations|the talkpage]].
* {{strong support}}. --[[User:Joalpe|Joalpe]] ([[User talk:Joalpe|talk]]) 01:58, 3 December 2020 (UTC) Justification: References are often not well structured in my context --which is something I'd assume happens in other Global South contexts--, which may lead to a lot of effort to create refined references for Wikipedia. It is fine to do it once and then have this structuring effort be reused in other articles; this is not what happens now, as editors end up redoing this every time they want to use the same reference in a different article.
* {{strong support}}. --[[User:Silva Selva|Silva Selva]] ([[User talk:Silva Selva|talk]]) 02:00, 3 December 2020 (UTC)
* {{strong support}}. --[[User:Erokhin|Erokhin]] ([[User talk:Erokhin|talk]]) 05:31, 3 December 2020 (UTC)
* {{support}} This would significantly improve citation management, reducing redundancy on any given wiki and between the different multilingual wikis, and also make it a lot easier to use different citation formats if people want. [[:en:Template:Cite Q]] does something similar, but only for references with their own Wikidata item; extending it to all references would be great. [[User:Mike Peel|Mike Peel]] ([[User talk:Mike Peel|talk]]) 13:55, 3 December 2020 (UTC)
* {{strong support}}. This proposal is the natural evolution of the [[WikiCite]] initiative and a sensible solution to bridge the gap between the horrible mess of citation management in Wikipedia with the abstract world of source metadata in Wikidata. There are still many open ended questions to answer, but I am strongly supportive of this proposed direction, which I see as a pragmatic, incremental solution to managing sources across Wikimedia projects. (Full disclosure: I was formerly the PI of the WikiCite grant and a WMF employee. I currently serve on the WikiCite steering committee as a volunteer) --[[User:DarTar|DarTar]] ([[User talk:DarTar|talk]]) 03:47, 4 December 2020 (UTC)
[[Category:WikiCite]]
* {{strong support}} - This is so badly needed in our movement and is the logical progression of centralizing our knowledge in images (Commons), factual claims, and language links (Wikidata). The implications for knowledge equity, verifiability, and reliable sourcing are profound. We would be able to maintain references and accurate information across all our projects and quickly ascertain how this information is being used. Structuring the references and citations in a modern, machine-readable database (rather than the current lexical, redundant, and inconsistent <nowiki><ref></nowiki> tags we have now) would be transformative. It would not just be an asset for Wikimedia projects, but would have implications for partners, GLAM organizations and scholarship globally. This is the next logical step for the WikiCite project and builds on great experiences and technology we have several years of activity within the working group. -- [[User:Fuzheado|Fuzheado]] ([[User talk:Fuzheado|talk]]) 14:57, 4 December 2020 (UTC)
* {{strong support}} I've been around with WikiCite since its inception, and followed countless discussions about reconciling the various directions this project could go. This is what we need to try to do in the next years, since we have the software and the mindset to make it evolve into a project that would serve Wikidata, all the other WMF projects ''and'' third parties. I am wholeheartedly all for it. [[User:Sannita|Sannita]] - <small>''[[User talk:Sannita|not just another it.wiki sysop]]''</small> 15:07, 4 December 2020 (UTC)
* {{strong support}} Since starting the Wikipedia Library in 2011, there has been a need for rational citation infrastructure. This sensible proposal takes a good crack at this hard problem. It would benefit hundreds of wikis and it promises to reduce time spent adding references to Wikimedia projects. Reliability and verifiability are at the heart of our reputation and functioning as a community; this proposal gets us one big step closer to our mission. Great work! [[User:Ocaasi|Ocaasi]] ([[User talk:Ocaasi|talk]]) 18:21, 4 December 2020 (UTC)
* {{strong support}} I have worked for years for this kind of project to be possible. It would be a crucial step in our community's work to verify content, it does not create unfunded mandates for communities, and has an information structure which allows tight integration with Wikidata without requiring or forcing it. It could potentially make the experience of editing Wikipedia more user-friendly and would vastly reduce the maintenance burden of Wikipedia's overworked labor. [[User:Harej|harej]] ([[User talk:Harej|talk]]) 19:35, 4 December 2020 (UTC)
* {{strong support}} I agree wholeheartedly with all the expressions of support outlined above. In my view this proposal has the potential to solve many of the citation and reference issues currently being faced by the plethora of WMF projects as well as aid the editing community contributing to the same. [[User:Ambrosia10|Ambrosia10]] ([[User talk:Ambrosia10|talk]]) 21:22, 4 December 2020 (UTC)
* {{strong support}} The best time to fix this is fifteen years ago; the second-best is now. Whatever the eventual solution looks like, this is a nettle we should grasp as soon as possible. <span class="vcard"><span class="fn">[[User:Pigsonthewing|Andy Mabbett]]</span> (<span class="nickname">Pigsonthewing</span>); [[User talk:Pigsonthewing|Talk to Andy]]; [[Special:Contributions/Pigsonthewing|Andy's edits]]</span> 21:35, 4 December 2020 (UTC)
* {{strong support}}Great to see this problem being tackled so comprehensively. One of the hardest things for me to accept as a new editor was the way citations are handled in Wikipedia.[[User:DrThneed|DrThneed]] ([[User talk:DrThneed|talk]]) 22:24, 4 December 2020 (UTC)
* {{strong support}} You had me at "Make citations easier for the editor, more useful for the reader, and more efficient for our architecture." --[[User:Rosiestep|Rosiestep]] ([[User talk:Rosiestep|talk]]) 22:57, 4 December 2020 (UTC)
* {{strong support}}. Hugely needed - timely - I support as an editor & information science researcher. This is important for flagging misinformation/retractions as well as for improving the reliability ("says who?") of Wikipedia-based info in other web information systems. Would save editor & reader time. Excellent use cases! [[User:Jodi.a.schneider|Jodi.a.schneider]] ([[User talk:Jodi.a.schneider|talk]]) 22:58, 4 December 2020 (UTC)
* {{s}} per Fuzheado and Andy Mabbett, and for the potentially massive reduction in the bloat of Wikidata items (said bloat having been a burden to usability of the knowledge base in some cases) that implementing this database would represent for a large class of items. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:26, 4 December 2020 (UTC)
* {{strong support}}. --[[User:Mlemusrojas|Mlemusrojas]] ([[User talk:Mlemusrojas|talk]]) 01:10, 5 December 2020 (UTC)
* {{strong support}} Yes please. sounds like an excellent solution to a much lamented problem. [[User:Doctor 17|Doctor 17]] ([[User talk:Doctor 17|talk]])
* {{strong support}} As a Wiktionary editor, I'll be happy to add easily a new example with the reference already formatted properly. As a [[:fr:wikt:Wiktionnaire:Actualités|wiki newspaper]] editor, I'll be happy to know how many country provide examples of use, how many examples are publication prior to a certain date, how many examples are by women, the division between examples from books, journal, website, etc. All those information may help to balance an unfair provenance of information, like adding more example from Senegal or wrote by women. I also support the way this proposal was made, and the implication of the authors to include perspectives from as much projects as possible! Great job here! -- [[User:Noé|Noé]] ([[User talk:Noé|talk]]) 14:35, 5 December 2020 (UTC)
* {{support}} Nicely compact and internationalizable. Helps us make footnotes in languages we don’t know. — [[User:Econterms|econterms]] <small>([[User_talk:Econterms|talk]])</small> 15:25, 5 December 2020 (UTC)
* {{strong support}}. This would be very valuable also for research purposes. [[User:Giovanni1085|Giovanni1085]] ([[User talk:Giovanni1085|talk]]) 15:27, 5 December 2020 (UTC)
* {{strong support}} Amazing, comprehensive plan. I am glad to see such an important project taking off. [[User:TiagoLubiana|TiagoLubiana]] ([[User talk:TiagoLubiana|talk]]) 20:15, 5 December 2020 (UTC)
* {{strong support}} This proposal will enable Wikipedians to save and use citation data in a shared citations database, which I would compare to what reference management software are used for writing scientific articles. The advantages are numerous as outlined here and the strong focus on the integration and tools for the Wikipedia community is convincing. --[[User:Zuphilip|Zuphilip]] ([[User talk:Zuphilip|talk]]) 20:51, 6 December 2020 (UTC)
* {{s}} A better solution for citations is indeed needed. Interoperability must be taken into account in all aspects. I don't think it's a trivial task. From my science perspective, I see these needs (they may be touched upon, but still reading the full text and all details): 1. "main subject" ability: being able to link literature to other things is what citable content in Wikidata so important (think Scholia); 2. being able to use the citations as references in Wikidata; 3. author names are non-trivial; reference types are non-trivial: it must have a detailed, documented model (think RIS, BibLaTeX, CSL). Basically, the model must be a superset of all we need (articles, software, data, chapters, books, etc, etc, etc), to ensure we will not get edit-wars and allow full curation. ShEx comes to mind as supporting tool; 4. seek connection with university libraries who are looking for open infrastructures to support their work. I hope to find time to read all the details next week. --[[User:Egon Willighagen|Egon Willighagen]] ([[User talk:Egon Willighagen|talk]]) 11:02, 7 December 2020 (UTC)
* {{strong support}}. This seems like a logical first step in structuring, standardising and improving citations on Wikipedia, and should make it easier for users to make that all important journey from Wikipedia article to reliable source material. [[User:Jason.nlw|Jason.nlw]] ([[User talk:Jason.nlw|talk]]) 10:31, 9 December 2020 (UTC)
* {{strong support}}. It is a no-brainer that this would be enormously helpful. At the same time, spontaneously it is less clear ''how'' to do it exactly—but I am amazed about the herein proposed implementation which has obviously taken into account a lot of experiences with our other projects. Great job so far! —[[User:MisterSynergy|MisterSynergy]] ([[User talk:MisterSynergy|talk]]) 13:51, 9 December 2020 (UTC)
* {{strong support}}. A very valuable project. A lot of work but really worth to do. [[User:Raymond|Raymond]] ([[User talk:Raymond|talk]]) 09:00, 10 December 2020 (UTC)
*{{strong support}} Thank you for pushing it forward with this well thought out plan! – [[User:Susannaanas|Susanna Ånäs (Susannaanas)]] ([[User talk:Susannaanas|talk]]) 12:55, 14 December 2020 (UTC)
* {{strong support}} This seems like a great next step for WikiCite. Reusing citations across Wikimedia projects in a standard way makes so much sense and I think libraries would be excited to contribute and help move this forward. [[User:Chicagohil|Chicagohil]] ([[User talk:Chicagohil|talk]]) 06:34, 15 December 2020 (UTC)
*{{strong support}} I agree that it's a logical extension of centralized images, language links and data. Desperately useful even just from a synchronisation point of view, but also monitoring and improving source usage across the sites. Early experiments by the wikicite community have laid the groundwork for what this would look like, but significant technical integration is needed for usability (especially with citoid). [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 11:28, 17 December 2020 (UTC)
* {{strong support}}. Such an important project. Also very well planned. I hope it starts working -- and soon! -- [[User:GiFontenelle|GiFontenelle]] ([[User talk:GiFontenelle|talk]]) 13:39, 19 December 2020 (UTC)
* {{strong support}}, this is logically the next best step for WikiCite to evolve from the existing scenario. -- [[User:Bodhisattwa|Bodhisattwa]] ([[User talk:Bodhisattwa|talk]]) 07:06, 3 January 2021 (UTC)
* {{strong support}}, we recently organized an event on WikiCite in Ghana where we partnered with a library and we were enlightened on how to get access to references using books etc. It really helped us on how to use citations. So this project is very important for the movement. [[User:DaSupremo|DaSupremo]] ([[User talk:DaSupremo|talk]]) 00:09, 4 January 2021 (UTC)
* {{strong support}}, it is a logical step, the evolution of the wikiverse after wikidata and wikifunctions makes mandatory a project like this.--[[User:TaronjaSatsuma|TaronjaSatsuma]] ([[User talk:TaronjaSatsuma|talk]]) 16:01, 4 January 2021 (UTC)
* {{strong support}}. What excites me most about this proposal is that it addresses the specific urgent need for better citation management in Wikipedia projects, while leaving the door open to ambitious open catalog efforts in Wikidata/Wikicite/etc in the future. The improvements in editing workflow, reading experience, library integrations, and epistemic confidence/quality are hard to overstate. --[[User:Blnewbold|Blnewbold]] ([[User talk:Blnewbold|talk]]) 21:41, 4 January 2021 (UTC)
* {{strong support}} - This is a wonderful proposal for me as an editor in a small language Wikipedia project. I use the content translation tool a lot for creating new pages. Usually once I have translated the article, then starts the cumbersome task of copying and adding citations to the new article, and inevitably template migration of references templates as well. This task of adding citations, usually takes as much time, it takes to translate the article in the first place. This project would cut-down my translation time in HALF!!, I strongly support this proposal. -- [[User:Thuvack|Thuvack]] ([[User talk:Thuvack|talk]]) 16:05, 6 January 2021 (UTC)
* {{strong support}}. I am full favour of any project that offers to reduce the effort required to create citations, the ease with which they can be reused, and the consistency with which they are recorded. This looks very promising and I look forward to seeing the results when they emerge.[[User:DrThneed|DrThneed]] ([[User talk:DrThneed|talk]]) 23:17, 7 January 2021 (UTC)
* {{strong support}}. I am in full favour! Example: same reference used to support multiple Wikidata statements, the same references are used in the Wikipedia article. [[User:David Nind|David Nind]] ([[User talk:David Nind|talk]]) 21:48, 10 January 2021 (UTC)
* {{strong support}} of course we need to expand and improve our citations infrastructure: to make our collection of bibliographic open knowledge more robust, to give reliability in articles a stronger foundation, to make editing easier for editors, and to support small languages. -- [[user:phoebe|phoebe]] | <small>[[user_talk:phoebe|talk]]</small> 20:05, 25 January 2021 (UTC)
*{{Support}} All of this makes sense. Just a few days ago, a new article was created on the English Wikipedia about a scientist who is an author of several books and papers cited in other articles. To add links from existing appearances of her name in other articles to the new article, I had to search for several different spellings of her name and to use various template parameters like editor-link or author-link instead of the familiar <nowiki>[[link syntax]]</nowiki>, even though most of the instances were from the same three books! This added up to about fifty edits, and this is just one of the times that I had to do it. In some other cases it's way more than fifty. Such things have to be done by lots of editors, and in many, many thousands of cases. The current infrastructure was good for adding a lot of references, but it doesn't scale. If we had a system proposed on this page, it would take much fewer edits—not fifty, but three or four, or maybe even zero. '''One important comment''': To realize the proposed system's full potential, the [[mw:Global templates/Proposed specification, short version|global templates and modules]] repository needs to be impemented, too, because almost all structured references are inserted into articles using templates and modules. As I write this, global templates are already mentioned here, and it's good, but it bears repeating: the two projects will really help each other, and both should be implemented. --[[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:14, 27 January 2021 (UTC)
* {{strong support}} --[[User:So9q|So9q]] ([[User talk:So9q|talk]]) 07:25, 10 February 2021 (UTC)
* {{strong support}}. It seems to me that this would be a magnificent and very important, possibly fundamental, addition to the Wikiverse. If nothing else, the accumulation and integration of this kind of data in the public domain might help to loosen the stranglehold that academic publishing has on academia, medicine, and scientific and technological progress in general. Once established and being used widely, I suspect it will generate a natural "pressure" or gradient, to expand and encompass more than just items cited in sister projects. — [[User:Jonathanischoice|Jonathanischoice]] ([[User talk:Jonathanischoice|talk]]) 21:35, 14 February 2021 (UTC)
* {{strong support}}. This is a solid approach to an issue that has been festering for a very long time. As a Wikidatan who adds many identical references every day, I am well aware of the massive duplication of data and effort involved in the current processes. - [[User:PKM|PKM]] ([[User talk:PKM|talk]]) 22:49, 14 February 2021 (UTC)
* {{strong support}} This is core to our projects. [[User:Mauricio V. Genta|Mauricio V. Genta]] ([[User talk:Mauricio V. Genta|talk]]) 19:01, 15 February 2021 (UTC)
* {{support}} A fascinating idea which should help with verifiability and transparency. [[User:Richard Nevell|Richard Nevell]] ([[User talk:Richard Nevell|talk]]) 09:45, 17 February 2021 (UTC)
* '''Bien sûr'''. Commented on earlier drafts; this is looking tremendous. Hurry up and take my cites. –[[User:Sj|SJ]]<small> [[User Talk:Sj|<font style="color:#f90;">talk</font>]] </small> 17:51, 19 February 2021 (UTC)
* {{strong support}} This makes a whole lot of sense. Working with citations through and across articles has taught me the difficulties of filing and duplicating templates, and maintaining references over time ; translating across Wikipedia versions has shown the pain of remapping template fields ; working with references on Wikidata has been a glimpse of what could be a 'nicer' reference editing experience, but crashed again the tediousness of reusing them across statements and items. The proposal is well researched and thought-through, drawing from relevant past projects (aaah, the ''Espace référence''!) and reflects on the needs of various Wikimedia projects beyond Wikipedia (particularly glad to see the Wiktionaries involved here!). It’s a tremendous opportunity. [[User:Jean-Frédéric|Jean-Fred]] ([[User talk:Jean-Frédéric|talk]]) 17:05, 22 February 2021 (UTC)
* {{support}} an important and ambitious idea, the problem is real and solutions need to be explored. Cdlt, [[User:VIGNERON|V<span style="font-size:75%">IGNERON</span>]] * [[User talk:VIGNERON|<sup>discut.</sup>]] 21:29, 22 February 2021 (UTC)
* {{support}} Complex, but definitely useful and interesting proposal --[[User:Lucamauri|LucaMauri]] ([[User talk:Lucamauri|talk]]) 08:01, 23 February 2021 (UTC)
* {{strong support}}. It is high time this will be deployed! [[User:Exec8|Exec8]] ([[User talk:Exec8|talk]]) 08:52, 23 February 2021 (UTC)
* {{strong support}}. --[[User:Olea|Olea]] ([[User talk:Olea|talk]]) 12:39, 23 February 2021 (UTC)
* {{strong support}}. This kind of centralized management of citations would also greatly simplify research projects aiming at understanding how knowledge is constructed in Wikipedia, and how Wikipedia in turn influences scientific knowledge construction. --[[User:Diegodlh|Diegodlh]] ([[User talk:Diegodlh|talk]]) 17:01, 23 February 2021 (UTC)
* {{strong support}}. This is very much needed, and the proposal looks great! --[[User:Akorenchkin|Akorenchkin]] ([[User talk:Akorenchkin|talk]]) 17:40, 23 February 2021 (UTC)
*{{strong support}} - A logical next step in handling sources. Just as commons handles images, and the possible global templates/modules. Interoperability is an oft-overlooked aspect of [[w:FAIR data|FAIR open practices]]. Sources are a key aspect of all wikimedia projects and so it has the potential for project-wide benefits (not just wikipedias). [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 10:02, 25 February 2021 (UTC)
*{{support}} This seems a neat idea, and if it leads to one being able to reuse citations of the same book (or journal article or legal decision or report) but with different page citations—as seems to be suggested—that'd be worth it generally. There are almost certainly going to be issues regarding community acceptance on-wiki if it is Wikidata based, and the Wikidata community probably need to have a bit of soul searching about how vandalism on Wikidata is handled, given that WikiCite potentially means vandalising one Wikidata object could affect thousands of Wikipedia articles across many projects and languages. The idea is good though and if the practical and community issues can be resolved, well worth pursuing. —[[User:Tom Morris|Tom Morris]] ([[User talk:Tom Morris|talk]]) 21:45, 26 February 2021 (UTC)
*{{support}} it was time...--[[User:Alexmar983|Alexmar983]] ([[User talk:Alexmar983|talk]]) 12:03, 28 February 2021 (UTC)
*{{reject}} I fail to see how it will make life easier. It rejects the existing information particularly for scholarly works. When it is to start from scratch AND insists that it will include everything with citations in Wikidata it will become a maintenance nightmare with any luck, the structured data that is already in Wikidata will save that day. Thanks, [[User:GerardM|GerardM]] ([[User talk:GerardM|talk]]) 12:33, 28 February 2021 (UTC)
*{{reject}} There are known citation biases. See [https://www.washingtonpost.com/politics/2021/02/24/wikipedias-political-science-coverage-is-biased-i-tried-fix-it/ Wikipedia’s political science coverage is biased. I tried to fix it.] I do not support this proposal in its current form, as the problem statement does not include bias at the highest level. For example: "Our references are high in maintenance, technical complexity, and duplication of effort." AND amplify and reinforce existing biases against groups that are already underrepresented in academia and elsewhere. This needs to be stated at the top as a significant component of the problem at hand, and metrics for success must include progress towards equity--and specifically gender equity. [[User:OpenSexism|OpenSexism]] ([[User talk:OpenSexism|talk]]) 22:36, 28 February 2021 (UTC)
**Ensuring Community and epistemological diversity was 'baked in' to the proposed [[WikiCite/Shared Citations#Rollout & Metrics|Rollout & Metrics]] and described somewhat in the [[WikiCite/Shared Citations#Knowledge Equity|Knowledge Equity]] subheading - but you're right that it did not explicitly name gender-equity (e.g. gender ratio of authors cited in references). In addressing content biases, it is hoped that being able to centralise and thereby quantify/analyse the currently used references, this will bring greater visibility to existing biases. This doesn't "solve the problem" by itself, but makes it harder to ignore by shedding light on the issue. For example, [[User:Noé]] had some interesting theoretical uses for French-Wiktionary in this direction – being able to highlight when a page didn't have any references from use-cases/pronunciations from beyond mainland France. p.s. for what it's worth, I've now added an explicit gender-analysis example to the [[WikiCite/Shared Citations#Use cases|table of use-cases]]. [[User:LWyatt (WMF)|LWyatt (WMF)]] ([[User talk:LWyatt (WMF)|talk]]) 15:23, 1 March 2021 (UTC)
**:Yeah, that's right. As I am invoked here, I want to say I am still eager to see this project on the rails. Well, in Wiktionaries, we are concerned by references but also by quotations to show the uses of the words described. For those, we will be pleased to be able to map the provenances of the books quoted and the gender of the people who wrote those quotations, including with more subtle data such as the genre of publication related to the gender (are women writers are more common in press articles or in theatrical pieces? are they more common after 1940s publications? are they more common in publication from Mali than from Senegal?). The Wiktionary community doesn't expect Shared Citations project to contribute to the Wiktionaries on this basis. It is a precious metrics to impulse other communities actions, if they want to, but I am convinced that it can't be expected to make the edits in every projects when it could only be made by the whole movement involvement [[User:Noé|Noé]] ([[User talk:Noé|talk]]) 17:36, 1 March 2021 (UTC)
** Thanks, Liam and Noé. Gaps and biases are a significant problem, as large as the ones listed in the proposal's problem statement, and equally relevant. The findings of the writer in The Washington Post story speak to a very deep problem that isn't represented among those driving this work. If knowledge equity is fundamental to the goals of the movement, it is also fundamental to the problems that must be solved. It's great that you noted a use case for gender bias research, but the existence of gender bias and other harmful biases is known, and belongs beside the other established problems and goals that motivate this work (verifiability, anti-disinformation, knowledge integrity, duplication, repetition, manual effort). It's much easier to understand that something is a priority--one that people care deeply about and are committed to realizing/solving--when it's at the top. Is there a reason not to do this? [[User:OpenSexism|OpenSexism]] ([[User talk:OpenSexism|talk]]) 17:56, 2 March 2021 (UTC)
::* Liam has been graciously discussing these comments and incorporating changes. If you have thoughts about how to better align existing and proposed systems to the goal of understanding, monitoring, and redressing citation biases, please join the discussion [[Talk:WikiCite/Shared_Citations#Adding_Bias_to_Problem_Statement/Goals | here]]. I am leaving these comments as they stand to '''draw attention to the problem and the need for resources''' [[User:OpenSexism|OpenSexism]] ([[User talk:OpenSexism|talk]]) 18:14, 14 March 2021 (UTC)
* {{strong support}}. As a keen reference user and contributor, and staunch believer in reliable sources of information, I support this. If it can be achieved, it would assist the whole project from the macro to the micro level. At the macro level - alignment with Wikipedia purpose, better functionality, enhanced reputation and ease of use; at the micro level - consistency down to the spelling of authors’ names. It would improve everything from contributing references to accessing them, making the encyclopaedia even more valuable. [[User:Whiteghost.ink|Whiteghost.ink]] ([[User talk:Whiteghost.ink|talk]]) 23:44, 28 February 2021 (UTC)
* {{strong support}} [[User:Kpjas|Kpjas]] ([[User talk:Kpjas|talk]]) 19:00, 1 March 2021 (UTC)
* {{support}} I have some questions on details, but this proposal makes a lot of sense to me. [[User:ArthurPSmith|ArthurPSmith]] ([[User talk:ArthurPSmith|talk]]) 21:00, 1 March 2021 (UTC)
* {{strong support}} [[User:Andrawaag|Andrawaag]] ([[User talk:Andrawaag|talk]]) 14:52, 2 March 2021 (UTC)
* {{strong support}} it'd be incredibly useful to have this for Wikidata. [[User:Nicereddy|Nicereddy]] ([[User talk:Nicereddy|talk]]) 01:48, 3 March 2021 (UTC)
* {{support}} The project already sum up how meaningful it could be, no need to paraphrase it here. My only concern is on the license, since it talk about Wikidata, which so far as only used CC-0 license. A the project page state, "Wikimedia’s citations are one of our greatest assets". and I my personal opinion is that throwing this asset under such a license is not the most efficient way to protect and foster it as a perennial heritage. Now, that doesn't invalid the clearness and importance of the issue this project means to address. Thank you for all that was already done. --[[User:Psychoslave|Psychoslave]] ([[User talk:Psychoslave|talk]]) 09:21, 17 March 2021 (UTC)
* {{strong support}} --[[User:Hfordsa|Hfordsa]] ([[User talk:Hfordsa|talk]]) 05:04, 19 March 2021 (UTC)
* {{strong support}}, and I've been urging this since I joined. But I just added the question about multiple version to the open question list; from my experience as a serials librarian, this can be surprising difficult; from my experience a a Wikipedia editor, a great many existing citations are incomplete or in error. [[User:DGG|DGG]] ([[User talk:DGG|talk]]) 03:42, 26 March 2021 (UTC)
* {{strong support}} [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 18:17, 16 April 2021 (UTC)

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit/Report

2021-01-18T22:36:14Z

Bryandamon: /* Grant funds spent */ Added link to Cover Letter.

{{Rapid Grant report|Status=Under review|Date=2018-19|Grantee=organization|Type=Final}}

==Goals==
The [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]] are now [https://mwstake.org/mwstake/img_auth.php/2/23/EIN_Application_and_Confirmation.pdf incorporated] and [https://mwstake.org/mwstake/img_auth.php/8/8b/IRS_Confirmation_of_non-profit_status.pdf recognized] as a non-profit, 501(c)(6) by the IRS. The process took longer than expected, however we are happy with the results and very grateful to the WMF for providing the grant.

==Outcome==

{{Project/Rapid/Report/Table/Header1}}



{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Determine which type of non-profit is best for the [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]] (MWStake)
| achieved outcome = MWStake decided on 501(c)(6)
| explanation = After [https://mwstake.org/mwstake/wiki/MWStake_incorporation/Non-profit_type investigation], MWStake decided on becoming a 501(c)(6)
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Minimize lawyer costs by doing as much work ourselves
| achieved outcome = We largely developed the [https://mwstake.org/mwstake/wiki/Bylaws MWStake Bylaws] on our own
| explanation = Many thanks to Frank Taylor who helped us create our own Bylaws saving us a much larger lawyer bill
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Incorporate the MWStake in the USA
| achieved outcome = MWStake has been incorporated
| explanation = The State of Pennsylvania has [https://mwstake.org/mwstake/img_auth.php/b/b9/Pennsylvania_Dep._of_State_Bureau_of_Corps_and_Charitable_Orgs..pdf recognized] MWStake as an incorporated entity in addition to the IRS [https://mwstake.org/mwstake/img_auth.php/2/23/EIN_Application_and_Confirmation.pdf recognition].
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Approval from the IRS for non-profit status
| achieved outcome = The IRS now [https://mwstake.org/mwstake/img_auth.php/8/8b/IRS_Confirmation_of_non-profit_status.pdf recognizes] MWStake as a non-profit
| explanation = We are now able to accept grants, membership dues, and other activities based on our non-profit status
}}


{{PEG/Proposals/Reports/Final/Table/1/End}}

==Learning==
#What worked well?
#* Developing our own [https://mwstake.org/mwstake/wiki/Bylaws Bylaws] allowed us to complete the project using much less money than expected ($2,410 actual vs. $3,500 expected).
#* Having our own members involved early gave us much more in-depth insight into some choices (non-profit type, entity structure, bylaw creation, etc.) which allowed us to make better decisions
# What did not work so well?
#* Our original timeline was way to aggressive given all of our prior commitments and the general pace of incorporate/lawyers
# What would you do differently next time?
#* More realistic schedule

==Finances==

===Grant funds spent===
As detailed on the [https://mwstake.org/mwstake/wiki/MWStake_incorporation#Costs MWStake website], the following was spent:

{| class="wikitable" style="margin-left:5em;"
|-
! Cost !! Description !! Notes
|-
| $125 || File Articles of Incorporation || rowspan="4" | Part of [https://mwstake.org/mwstake/img_auth.php/9/91/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 || [https://mwstake.org/mwstake/img_auth.php/f/f0/Cover.pdf Check sent] to Smoker Gard made out to US Treasury
|-
| $1,430 || [https://mwstake.org/mwstake/img_auth.php/c/ce/Smoker_Gard_Invoice_2.pdf Invoice #2] || Final invoice
|-
|- style="border-top-style: double;"
! $2,410 || colspan="2" style="text-align:left;" | Total
|}

===Remaining funds===
We have spent all the grant funds ($2,000), the difference in what we owe ($2,410) will be raised by seed money from board members.



==Anything else==
We would like to thank the WMF for the grant and are looking forward to benefiting the 3rd party MediaWiki community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki.

[[Category:Project/Rapid/Report]]

Wikimedia Clinics

2020-09-11T09:00:09Z

Bryandamon: Undoing changes by 118.136.110.195, obvious vandalism.

This page documents an experimental Wikimedia Foundation program called '''Wikimedia Clinics''', coordinated by the Community Development team, and archives the notes generated during the Clinic calls.

==About the program==
In these complex times of pandemic, and the coming complex times of post-pandemic, live human contact with fellow Wikimedians, even mediated through a video call, can be helpful, relaxing, and fun. It can also offer opportunities to ask questions you have been meaning to ask but never got around to, or to explain complex situations that may be hard to articulate in writing.

To better support members of the community during this time, the Community Development team is scheduling open video calls where any active Wikimedian is welcome to attend and ask questions or ask for advice about whatever Wikimedia-related goal or problem they're working on.

You can also just share what you're working on and invite feedback, even if you don't have a specific question. Or people can just connect to hang out, or to offer their own experience to the people asking questions.

These calls will be hosted two to three times a month (in alternating time zones, to accommodate as many people as possible).

Each clinic session:
* would be 70-90 minutes in length depending on topics presented and volume of conversation
* would have at least two Wikimedia Foundation staff members guaranteed to be present. They are not guaranteed to have the answers you need, but they are committed to helping you get them, even if not during the call itself, but as later follow-up.
* would be summarized in an in-depth '''digest''' of the call that would be edited for clarity and available to all volunteers interested. These notes would link to any tools and resources mentioned on the call and will be shared on this mailing list and archived on Meta (below).

These calls are '''not''' replacing any existing channels or regularly-scheduled calls! Every channel or call you are already using continues to exist. No important announcements will be made on these calls, and no one should feel stressed or obligated to attend them.

Rather, they are a new form of live-communication open support calls, less narrow in focus than some of the existing channels (where only specific topics are expected), and, we hope, more approachable and welcoming for people not sure whether their question or dilemma is appropriate for one of the other channels.

If these calls are found useful, we'll try to offer them in some other languages, to increase access to those not comfortable speaking English.

==Expected conduct==
The Wikimedia Clinic calls are a [[Friendly space policy|Friendly space]]. Attendees are expected to:
* Listen with patience and respect.
* Share your experience, but remember others' contexts are very diverse, and may not match yours.
* Be of service to others on the call.

==Upcoming calls==
Based on feedback received so far, starting with Clinic #007, we have some <u>pre-scheduled segments</u> (so people can choose to attend if interested in those topics), but will still leave a good chunk of time in each call for people to bring up topics spontaneously.

The next calls are scheduled for:
* '''Wikimedia Clinic #010''', Tuesday, September 15th, 13:00 UTC, and this is the Google Meet link. Scheduled topic: '''Abstract Wikipedia''' with '''[[User:DVrandecic (WMF)|Denny Vrandečić]]'''. (Other topics welcome after scheduled segment!

Remember there's no particular preparation needed. Feel free to join us with anything '''Wikimedia-related''' that's on your mind, or just to hang out.

==Archive of digests of past calls==
{| class="wikitable"
|+
!#
!date
!topics
!language
|-
|001
|15-Jun-2020
|
* [[Wikimedia Clinics/001|Universal Code of Conduct]]
* [[Wikimedia Clinics/001|The wiki-specific nature of some of our challenges]]
* [[Wikimedia Clinics/001|Notability by country]]
* [[Wikimedia Clinics/001|Wikipedia Pages Wanting Photo]]<nowiki/>s
|English
|-
|002
|17-Jun-2020
|
* [[Wikimedia Clinics/002|Shared, global templates repository]]
* [[Wikimedia Clinics/002|WikiLambda/Abstract Wikipedia]]
* [[Wikimedia Clinics/002|New main page on Northern Sámi Wikipedia]]
* [[Wikimedia Clinics/002|Usability of Commons]]
* [[Wikimedia Clinics/002|Contributing to Wikimedia during the pandemic]]
* [[Wikimedia Clinics/002|on the Branding project]]
* [[Wikimedia Clinics/002|Populating information from Wikidata]]
* [[Wikimedia Clinics/002|Meta Profile]]
* [[Wikimedia Clinics/002|How to use information from Wikidata in other projects?]]
* [[Wikimedia Clinics/002|How to generate citations from Wikidata]]
* [[Wikimedia Clinics/002|Lexemes in Wikidata]]
* [[Wikimedia Clinics/002|Are there plans to improve Wikisource?]]
* [[Wikimedia Clinics/002|Grants & Events]]
|English
|-
|003
|23-Jun-2020
|
* [[Wikimedia Clinics/003|The term 'projects' and doing outreach]]
* [[Wikimedia Clinics/003|Increasing awareness of Wikimedia Commons]]
* [[Wikimedia Clinics/003|News on Wiki campaign]]
* [[Wikimedia Clinics/003|Universal Code of Conduct Drafting committee - call for volunteers]]
* [[Wikimedia Clinics/003|Education Office Hours]]
* [[Wikimedia Clinics/003|Ukrainian education program]]
* [[Wikimedia Clinics/003|Commons App]]
|English
|-
|004
|28-Jun-2020
|
* [[Wikimedia Clinics/004|Community friction in outreach on Turkish Wikipedia]]

* [[Wikimedia Clinics/004|Announcement about Celtic Knot 2020 Conference (Virtual)]]

* [[Wikimedia Clinics/004|Consultations between the WMF and the meta Community]]

* [[Wikimedia Clinics/004|Translation of the Template:Cite Q from English to Spanish?]]

* [[Wikimedia Clinics/004|International conflict observatory]]

* [[Wikimedia Clinics/004|Can you recall a great talk or presentation outside Wikimedia that really inspired your Wikimedia work?]]
|English
|-
|005
|1-Jul-2020
|
* [[Wikimedia Clinics/005|Generating tables on Wikipedia from Wikidata]]

* [[Wikimedia Clinics/005|Are you active in affiliates? Why or why not?]]
* [[Wikimedia Clinics/005|How to connect with local Wikimedians?]]
* [[Wikimedia Clinics/005|Datasets relating to Wikimedia activities by country?]]
* [[Wikimedia Clinics/005|ReplyTool]]
|English
|-
|006
|16-Jul-2020
|
{| class="wikitable"
|+
!Español
!English
|-
|[[Wikimedia Clinics/006|Impacto de la pandemia en los afiliados]]
|[[Wikimedia Clinics/006/en|Impact of the pandemic on affiliates]]
|-
|[[Wikimedia Clinics/006|Apoyo que se necesita de la Fundación]]
|[[Wikimedia Clinics/006/en|Needed support from the Foundation]]
|}
|Spanish
|-
|007
|05-Aug-2020
|
* [[Wikimedia Clinics/007|Statistics tools demonstrations (+Bonus demonstration of stylometric analysis to uncover sock puppets)]]
* [[Wikimedia Clinics/007|What is "Wikimedia research"]]
* [[Wikimedia Clinics/007|In person events]]
* [[Wikimedia Clinics/007|Wikimedia in Mainland China]]
* [[Wikimedia Clinics/007|Technical feedback on Jitsi]]
|English
|-
|008
|10-Aug-2020
|
* [[Wikimedia Clinics/008|WMF Research (Presentation by Leila Zia (WMF))]]
* [[Wikimedia Clinics/008|Wiki Studies]]
* [[Wikimedia Clinics/008|Pitching ideas for development to WMF]]
* [[Wikimedia Clinics/008|Harassment]]
|English
|-
|009
|21-Aug-2020
|TBD
|English
|}
[[Category:Community engagement]]
[[Category:Meetings]]

User:Bryandamon/common.js

2020-06-10T17:19:45Z

Bryandamon:

mw.loader.load("https://meta.wikimedia.org/w/index.php?title=User:Michael Schönitzer (WMDE)/timezoneconverter.js&action=raw&bcache=1&maxage=86400&ctype=text/javascript");

User:Bryandamon/common.js

2020-06-10T17:17:02Z

Bryandamon:

mw.loader.load("https://meta.wikimedia.org/wiki/User:Michael Schönitzer (WMDE)/timezoneconverter.js&action=raw&bcache=1&maxage=86400&ctype=text/javascript");

User:Bryandamon/common.js

2020-06-10T17:09:50Z

Bryandamon: Tried changing to meta

mw.loader.load("https://meta.wikimedia.org/wiki/User:Michael_Sch%C3%B6nitzer_(WMDE)/timezoneconverter.js&action=raw&bcache=1&maxage=86400&ctype=text/javascript");

User:Bryandamon

2020-06-10T17:05:53Z

Bryandamon: Testing User:Michael Schönitzer (WMDE)/timezoneconverter

{{softredirect|en:User:Bryandamon}}

{{User:Michael Schönitzer (WMDE)/Template:timezoneconverter}}

* {{User:Michael Schönitzer (WMDE)/Template:TZC event|2020|06|01|15|48}}
* {{User:Michael Schönitzer (WMDE)/Template:TZC event|year=2020|month=06|day=01|hour=15|minute=48}}

User:Bryandamon/common.js

2020-06-10T16:56:16Z

Bryandamon: Testing User:Michael Schönitzer (WMDE)/timezoneconverter

mw.loader.load("https://en.wikipedia.org/w/index.php?title=User:Michael Schönitzer (WMDE)/timezoneconverter.js&action=raw&bcache=1&maxage=86400&ctype=text/javascript");

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit/Report

2020-05-18T18:12:22Z

Bryandamon: Created page with " {{Rapid Grant report|Status=Draft|Date=2017-18|Grantee=organization|Type=Final}} ==Goals== The MediaWiki Stakeholders' Group are now [h..."

{{Rapid Grant report|Status=Draft|Date=2017-18|Grantee=organization|Type=Final}}

==Goals==
The [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]] are now [https://mwstake.org/mwstake/img_auth.php/2/23/EIN_Application_and_Confirmation.pdf incorporated] and [https://mwstake.org/mwstake/img_auth.php/8/8b/IRS_Confirmation_of_non-profit_status.pdf recognized] as a non-profit, 501(c)(6) by the IRS. The process took longer than expected, however we are happy with the results and very grateful to the WMF for providing the grant.

==Outcome==

{{Project/Rapid/Report/Table/Header1}}



{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Determine which type of non-profit is best for the [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]] (MWStake)
| achieved outcome = MWStake decided on 501(c)(6)
| explanation = After [https://mwstake.org/mwstake/wiki/MWStake_incorporation/Non-profit_type investigation], MWStake decided on becoming a 501(c)(6)
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Minimize lawyer costs by doing as much work ourselves
| achieved outcome = We largely developed the [https://mwstake.org/mwstake/wiki/Bylaws MWStake Bylaws] on our own
| explanation = Many thanks to Frank Taylor who helped us create our own Bylaws saving us a much larger lawyer bill
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Incorporate the MWStake in the USA
| achieved outcome = MWStake has been incorporated
| explanation = The State of Pennsylvania has [https://mwstake.org/mwstake/img_auth.php/b/b9/Pennsylvania_Dep._of_State_Bureau_of_Corps_and_Charitable_Orgs..pdf recognized] MWStake as an incorporated entity in addition to the IRS [https://mwstake.org/mwstake/img_auth.php/2/23/EIN_Application_and_Confirmation.pdf recognition].
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Approval from the IRS for non-profit status
| achieved outcome = The IRS now [https://mwstake.org/mwstake/img_auth.php/8/8b/IRS_Confirmation_of_non-profit_status.pdf recognizes] MWStake as a non-profit
| explanation = We are now able to accept grants, membership dues, and other activities based on our non-profit status
}}


{{PEG/Proposals/Reports/Final/Table/1/End}}

==Learning==
#What worked well?
#* Developing our own [https://mwstake.org/mwstake/wiki/Bylaws Bylaws] allowed us to complete the project using much less money than expected ($2,410 actual vs. $3,500 expected).
#* Having our own members involved early gave us much more in-depth insight into some choices (non-profit type, entity structure, bylaw creation, etc.) which allowed us to make better decisions
# What did not work so well?
#* Our original timeline was way to aggressive given all of our prior commitments and the general pace of incorporate/lawyers
# What would you do differently next time?
#* More realistic schedule

==Finances==

===Grant funds spent===
As detailed on the [https://mwstake.org/mwstake/wiki/MWStake_incorporation#Costs MWStake website], the following was spent:

{| class="wikitable" style="margin-left:5em;"
|-
! Cost !! Description !! Notes
|-
| $125 || File Articles of Incorporation || rowspan="4" | Part of [https://mwstake.org/mwstake/img_auth.php/9/91/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
|-
| $1,430 || [https://mwstake.org/mwstake/img_auth.php/c/ce/Smoker_Gard_Invoice_2.pdf Invoice #2] || Final invoice
|-
|- style="border-top-style: double;"
! $2,410 || colspan="2" style="text-align:left;" | Total
|}

===Remaining funds===
We have spent all the grant funds ($2,000), the difference in what we owe ($2,410) will be raised by seed money from board members.



==Anything else==
We would like to thank the WMF for the grant and are looking forward to benefiting the 3rd party MediaWiki community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki.

[[Category:Project/Rapid/Report]]

Community Wishlist Survey 2020/Wikiversity/Simple structured input forms

2019-11-26T00:26:35Z

Bryandamon: /* Voting */ Adding my support.

{{:Community Wishlist Survey/Proposal header|1=Simple structured input forms}}

* '''Problem''': Information is often far better input via a form rather than editing wikimarkup ([https://meta.wikimedia.org/w/index.php?action=edit&preload=Community+Wishlist+Survey%2FPreload%2Fen&editintro=Community_Wishlist_Survey%2FEditintro&title=Community+Wishlist+Survey+2020%2FWikiversity%2Fwikimarkup+shouldn%27t+be+a+requirement+to+submit+a+proposal&create=Create+proposal like this page]). Especially when either A) the same fields will be repeatedly required or B) when new users are involved. New users are often put off my wikimarkup, even when templates and preloaded text is used ([https://en.wikiversity.org/w/index.php?title=Talk:WikiJournal_of_Medicine/Editors&action=edit&section=new&preload=WikiJournal_of_Medicine%2FEditorial_board%2FApplication&summary=Editorial+board+application example]). This leads to projects and affiliates often using google forms in stead then copy-pasting the information to wiki ([https://docs.google.com/forms/d/e/1FAIpQLSfP1MvuBmtCkqT7i5qYyIm0jspEL2wE440hWSD9tWLmMTFNKA/viewform example]). Currently a small number of [[phab:T149869|outstanding issues remain]] on the [[mw:Extension:Page_Forms|Pageforms Extension]] that could address this by making an in-house, general-purpose form tool with structured inputs.
* '''Who would benefit''':
**Would improve usability for new users and one-off wikimedians (e.g. GLAM, editathons, affiliate signups)
**Very valuable to replace [[w:template:preloaddraft]] and [[w:Template:User sandbox+]] for creating new articles with suggested sections.
**Would even be useful for simple maintainance items like [[v:wv:Requests_for_Deletion]].
:Example use case in wikiversity: It'd be great to be able to use [https://wikipediajournal.com/Special:FormEdit/Peer_review_submission/Review:test_article this peer review submission form] rather than the current system (peer reviews are submitted via [[wikiversity:WikiJournal_of_Medicine/Peer_reviewers#Peer_review_instruction_summary|this google form]], which deposits them to a [https://docs.google.com/spreadsheets/d/19ge5HgqVAzr7v9A8kqvBzhZ68Vti4HKTDev0HGbPMJI/edit#gid=0 google spreadsheet like this], where they're manually copied to the [[wikiversity:Talk:WikiJournal_of_Medicine/The_Cerebellum|relevant article talkpage]], and noted down on [[wikiversity:WikiJournal_User_Group/Potential_upcoming_articles|this tracking table]], and maybe at some point will have their metadata [[wikidata:Q44001486|added to Wikidata]]). Similarly useful for submitting articles in stead of [https://docs.google.com/forms/d/e/1FAIpQLSf-Nu7hjiTeJ5uQ5ozMOIivWZjeyJCPLwAUOuNDP1MVKUbCSQ/viewform this google form].
* '''Proposed solution''': A way of having structured forms to create and edit specific wiki pages that always have the same layout/format. Particularly useful capabilities listed below with submitting peer reviewer comments as the worked example:
:''Inputs:''
:#Free text box for content to be added to page section or inside template (e.g. the content of a peer review, or a faculty webpage)
:#Dropdown list or autocompleted textbox of predefined options to pick from:
:##Populated/autocompleted from wikidata like when typing into wikidata field (e.g. to pick affiliation from wikidata-listed organisations)
:##Populated/autocompleted from category (e.g. to specify [[wikiversity:Category:Articles_currently_submitted_to_a_WikiJournal_for_peer_review|which article is being reviewed]])
:##Hardcoded list (e.g. whether to have identity open or embargoed)
:##Tickbox that when clicked will add set text (e.g. declaration of no competing interests)
:#Ability upload of a file (e.g. [[wikiversity:Talk:WikiJournal_of_Medicine/Mealtime_difficulty_in_older_people_with_dementia#Comments_from_Reviewer_3|pdf of peer reviewer comments/annotations]])
:#Distinguish between required and optional fields
:#Ability to show additional fields based on what has previously been picked (e.g. if user states that they wish have their identity embargoed, box appears to ask them to provide description of credentials, or makes the credentials box required rather than optional)
:#Ability to pre-fill some of those fields using info in the URL (e.g. when link is sent via email to potential peer reviewer for specific article)
:#Submission button to convert those chosen options into the required wikitext and save to the specified page (e.g. [[wikiversity:Talk:WikiJournal_of_Medicine/Mealtime_difficulty_in_older_people_with_dementia|the peer review page]]).
:#Option to edit which fields are displayed depending on whether the submitting user is listed in a template, or on wikidata as either the submitting author
:''Outputs:''
:#Add text to page (e.g. the content of a peer review)
:#Create new page (e.g. when the first per review is submitted, create the talkpage)
:#Replace text in a specific page section or template
:#Update wikidata item (e.g. add {{P|P4032}})
:#Add file to commons or locally
:#Create new wikidata item (e.g. if reviewer provides ORCID, but wikidata item for them doesn't yet exist)
:#Add information to the user's hidden information (e.g. if they had not previously added an email address to their account, allow them to do so via the form, but eventually other info such as committed identity)
:Although it'd be useful to have as many of these functions as possible, I've tried to order them from most necessary to most optional.

* '''More comments''': Using more structured input has already been useful for (e.g. the [[c:Special:UploadWizard|commons upload wizard]]). A general solution for use in other contexts would be hugely useful. Possibly broader solution via Page_Forms: [[phab:T149869#5654801|T149869]]. See also [[wikidata:Wikidata:Bot_requests#Automated_addition_of_WikiJournal_metadata_to_Wikidata|bot request]] for related wikidata tasks.
* '''Phabricator tickets''':
* '''Proposer''': [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 04:04, 2 November 2019 (UTC)

===Discussion===
* No argument that this would be very useful. The phab ticket selection suggests that the main blocker on this is some outstanding security issues in the Page Forms extension ([https://phabricator.wikimedia.org/project/view/272/ Page Forms on Phab], and the [https://www.mediawiki.org/wiki/Extension:Page_Forms Extension page]). Is this the case, or are there other major issues? [[User:HLHJ|HLHJ]] ([[User talk:HLHJ|talk]]) 22:22, 3 November 2019 (UTC)
* Strong support. Better form input would help newer editors enter consistent information as well as being able to analyse the resulting structured data. This would be a big win across the board. — [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 22:07, 6 November 2019 (UTC)
*[[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]], thank you for submitting this proposal! We have one request: Can you provide more information on the problem? Right now, we mostly see information on the proposed solution, which we may or may not be able to implement. However, if you flesh out the problem a bit more (in the "Problem" section), we can have a better sense of the potential options to solve the issue. Thanks! --[[User:IFried (WMF)|IFried (WMF)]] ([[User talk:IFried (WMF)|talk]]) 04:51, 11 November 2019 (UTC)
*: {{re|IFried (WMF)}} Thanks. I've now expanded on it a little from a user point of view. Sadly I don't have enough knowledge to comment on the technical side of [[phab:T149869|T149869]]. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 05:17, 11 November 2019 (UTC)
*:: {{re|Evolution_and_evolvability}} Thanks for the update! Your changes helped clarify the problem. --[[User:IFried (WMF)|IFried (WMF)]] ([[User talk:IFried (WMF)|talk]]) 05:27, 11 November 2019 (UTC)
Unfortunately, this extension would require much more work to be deployable on WMF than it's assumed. We can't dedicate this amount of time to it because we will have other projects to work on next year. Regardless, thank you for participating in our survey! [[User:MaxSem (WMF)|MaxSem (WMF)]] ([[User talk:MaxSem (WMF)|talk]]) 00:58, 19 November 2019 (UTC)
:{{re|MaxSem (WMF)}} Is there scope for a stripped down version to be implemented that don't include the abilities that cause security issues? The main elements that would be the most useful are:
:*Saving text to a page
:*Updating a wikidata item
:*Creation of a new page
:*Upload of a file
:via any kind of structured form that can have e.g.:
:*Dropdown lists populated from wikidata or categories
:*Dropdown lists populated from set of options
:*Presentation of additional options based on those previously entered
:*Free text field
: [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 02:20, 19 November 2019 (UTC)
::[[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]], hello! We have discussed this as a team, and we think that this wish can be unarchived, if it has some changes. First, the wish should be rewritten to not imply that it will include deploying Page Forms. Second, we propose a change of title to something like 'provide a form to create new articles for wiki journal structures.' If these changes are made, the wish will be more flexible and manageable for us. Please make these changes before tomorrow at 18:00 UTC (which is when voting begins). Thank you! --[[User:IFried (WMF)|IFried (WMF)]] ([[User talk:IFried (WMF)|talk]]) 21:25, 19 November 2019 (UTC)
:::Ok, I'll edit up this page and move to a different tile to focus on the specific use case and requested capabilities rather than the extension itself. I'll add a link to this oldid so that people can see the earlier version if they wish. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 04:56, 20 November 2019 (UTC)
::::Initial submission titled "Extension:Page forms on WMF servers", see [https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey_2020/Archive/Extension:Page_forms_on_WMF_servers&oldid=19572322 this oldid]. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 01:51, 21 November 2019 (UTC)
*Just to be clear, this proposal is about installing the Cargo extension on Wikiversity, right? (As opposed to SemanticMediaWiki, which has been rejected already.) Or is it about making PageForms work without Cargo and with a different kind of "backend"? [[User:Nemo_bis|Nemo]] 09:13, 22 November 2019 (UTC)
-------------
I've updated the application to focus on specific capability set rather than any particular tool to achieve those capabilities. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 01:51, 21 November 2019 (UTC)

=== Voting ===
* {{support}} [[User:Libcub|Libcub]] ([[User talk:Libcub|talk]]) 08:48, 22 November 2019 (UTC)
* {{support}} [[User:Lionel Scheepmans|Lionel Scheepmans]] <sup><big>✉ </big> [[User talk:Lionel Scheepmans|Contact]]</sup> <sub>French native speaker, sorry for my [[w:dysorthography|dysorthography]]</sub> 11:03, 22 November 2019 (UTC)
* {{support}} To enable PageForms on Wikiversity, it will need to be improved to meet WMF code standards. Doing that will be hard work, but if accomplished, then it would be much easier to enable it on ''other'' wikis, which would help enormously to increase the amount and quality of contributions, since new users are much more familiar with forms than with wikitext. So enabling PageForms would benefit not just Wikiversity, but the Wikimedia movement generally. [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|talk]]) 13:52, 22 November 2019 (UTC)
* {{support}} [[User:Faendalimas|<span style="color: #004730">Scott Thomson</span>]] (<small class="nickname">Faendalimas</small>) <sup>[[User talk:Faendalimas|<span style="color: maroon">talk</span>]]</sup> 15:20, 22 November 2019 (UTC)
* {{support}} [[User:OhanaUnited|<b><font color="#0000FF">OhanaUnited</font></b>]][[User talk:OhanaUnited|<b><font color="green"><sup>Talk page</sup></font></b>]] 16:20, 22 November 2019 (UTC)
* {{support}} [[User:MavropaliasG|MavropaliasG]] ([[User talk:MavropaliasG|talk]]) 05:54, 23 November 2019 (UTC)
* {{support}} [[User:Stevenfruitsmaak|Steven Fruitsmaak]] <small>([[User_talk:Stevenfruitsmaak|Reply]])</small> 02:17, 25 November 2019 (UTC)
* {{support}} - this is long overdue and should be rolled out across all projects. Wikitext is essentially a markup language, looking far too much like a programming language (remember Wordstar markup before Word came alone, anyone?) and many years past its sell-by date. New users should be able to add a cited fact as a single entity, so that it is immediately obvious that the source and its attributes (author, date, ...) are part of the claim, which could naturally be thought of as "author A makes claim C on date D in journal J ..." rather than the current bald "C" [is unconditionally true (not)]. It would be transformative to do things properly. [[User:Chiswick Chap|Chiswick Chap]] ([[User talk:Chiswick Chap|talk]]) 09:36, 25 November 2019 (UTC)
* {{support}} [[User:Liuxinyu970226|Liuxinyu970226]] ([[User talk:Liuxinyu970226|talk]]) 15:40, 25 November 2019 (UTC)
* {{support}} [[U:游魂|<span style="color:purple;font-family:MS Pgothic;">'''游'''</span>]][[User talk:游魂|<span style="color:purple;font-family:MS Pgothic;">'''魂'''</span>]] 17:02, 25 November 2019 (UTC)
* {{support}} [[User:Smvital|Smvital]] ([[User talk:Smvital|talk]]) 06:10, 25 November 2019 (UTC)
* {{Strong support}} Better form input would help newer editors enter consistent information as well as being able to analyse the resulting structured data. This would be a big win across the board. — [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 00:26, 26 November 2019 (UTC)

Community Wishlist Survey 2020/Wikiversity/Simple structured input forms

2019-11-06T22:07:52Z

Bryandamon: Adding my endorsement.

{{:Community Wishlist Survey/Proposal header|1=Extension:Page forms on WMF servers|2=Edit proposal/discussion|year=2020}}

* '''Problem''': Information is often far better input via a form rather than editing wikimarkup (like this page). Especially when either A) the same fields will be repeatedly required or B) when new users are involved.
* '''Who would benefit''': Generally, would improve usability for new users and one-off wikimedians (e.g. GLAM and editathons). Also very valuable to replace [[w:template:preloaddraft]] and [[w:Template:User sandbox+]] for creating new articles with suggests sections. Example use case: It'd be great to be able to use [https://wikipediajournal.com/Special:FormEdit/Peer_review_submission/Review:test_article this peer review submission form] rather than the current system ( peer reviews are submitted via [[wikiversity:WikiJournal_of_Medicine/Peer_reviewers#Peer_review_instruction_summary|this google form]], which deposits them to a [https://docs.google.com/spreadsheets/d/19ge5HgqVAzr7v9A8kqvBzhZ68Vti4HKTDev0HGbPMJI/edit#gid=0 google spreadsheet like this], where they're copied to the [[wikiversity:Talk:WikiJournal_of_Medicine/The_Cerebellum|relevant article talkpage]], and noted down on [[wikiversity:WikiJournal_User_Group/Potential_upcoming_articles|this tracking table]], and maybe at some point will have their metadata [[wikidata:Q44001486|added to Wikidata]]). Would even be useful for simple maintainance items like [[v:wv:Requests_for_Deletion]].
* '''Proposed solution''': Finish fixing the last few bugs in [[mw:Extension:Page_forms]] in order to implement om WMF servers.
* '''More comments''': Using more structured input has already been useful for (e.g. the [[c:Special:UploadWizard|commons upload wizard]]). A general solution for use in other contexts would be hugely useful.
* '''Phabricator tickets''': [[phab:T149869|T149869]]
* '''Proposer''': [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 04:04, 2 November 2019 (UTC)

===Discussion===
* No argument that this would be very useful. The phab ticket selection suggests that the main blocker on this is some outstanding security issues in the Page Forms extension ([https://phabricator.wikimedia.org/project/view/272/ Page Forms on Phab], and the [https://www.mediawiki.org/wiki/Extension:Page_Forms Extension page]). Is this the case, or are there other major issues? [[User:HLHJ|HLHJ]] ([[User talk:HLHJ|talk]]) 22:22, 3 November 2019 (UTC)
* {{support|strong}} Better form input would help newer editors enter consistent information as well as being able to analyse the resulting structured data. This would be a big win across the board. — [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 22:07, 6 November 2019 (UTC)

Community Wishlist Survey 2020/Wikiversity/Autopopulate userpage starting info from ORCID

2019-10-30T03:16:23Z

Bryandamon: Minor spelling edits.

{{:Community Wishlist Survey/Proposal header|1=Autopopulate userpage starting info from ORCID|year=2020}}

* '''Problem''': When new users who already have an [https://orcid.org/ ORCID account] create a Wikimedia account, their userpage is initially blank despite useful info existing to populate it
* '''Who would benefit''': New Wikiversity users commonly have ORCIDs and also commonly edit under their real names. This may also be relevant to that subsection of the Wikipedia community who also does
* '''Proposed solution''': When new users sign up to Wikiversity, ask if they have an orcid account and whether they would like it to be used to initially populate their new userpage. Various levels of integration are possible, but may also be an initial step towards ORCID also listing wikimedia contribution [http://xtools.wmflabs.org/ec summary stats] or featured articles in ORCID profiles. See also [[ORCID|Meta:ORCID]].
* '''More comments''':
**Option 1) Just auto add an {{tlx|authority control}} template based on the orcid
**Option 2) Copy over basic information from ORCID to populate the userpage
**Option 3) Add/transclude their [[toolforge:scholia/author|scholia profile]] to the userpage
**Option 4) Allow users to verify their ORCID and associate it with their Wikimedia identity
**Option 5) Allow users to log in using their ORCID profile
* '''Phabricator tickets''': ([[Phab:T136943|T136943]] for option 4/5)
* '''Proposer''': [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 10:42, 29 October 2019 (UTC)

===Discussion===

Grants:Project/Rapid/SMWConFall2019/Video

2019-09-09T20:57:00Z

Bryandamon: Changed to proposed.

<div style="float:right; width: 24em">
{{Probox

|status= proposed

|grantee= Bryandamon

|contact= bryandamon{{@}}gmail.com

|project= MWStake/SMWCon2019Video

|affiliate= MW-SG

|summary= Provide funds for professional video production of the [https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2019 SMWCon Fall 2019] in Paris, France

|target= Third-party users, developers, and contribution to the MediaWiki product.

|start_date= September 25th

|start_year= 2019

|end_date= September 27th

|end_year= 2019

|amount_local= €1,813

|amount= $2,000

|grant_type= Group

|organization= [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]]

|contact2=

|website= [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]]

|nonprofit= We are finalizing out non-profit status with the IRS now. If the grant is accepted and can't be given to MWStake until the non-profit status is achieved, it can be given to the conference organizers Clément Flipo or Lex Sulzer.

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>

*Please see the sample [[Grants:Project/Rapid/Plan/SampleApplication/Video campaigns|Video campaign application]] before drafting your application.
*You can also read a recent video campaign application, [[Grants:IdeaLab/Promotion_Of_Punjabi_Wikipedia_On_Social_Media|Promotion of Punjabi Wikipedia on Social Media]] and their [[Grants:IdeaLab/Promotion_Of_Punjabi_Wikipedia_On_Social_Media/Report|related report]].

==Project Goal==
#Hold a three-day conference featuring discussions of topics related to "Enterprise MediaWiki", i.e. the usage of MediaWiki software by and within companies, non-profits, governments, and other organizations.
#Further the [https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Direction#Knowledge_as_a_service:_A_platform_that_serves_open_knowledge_to_the_world_across_interfaces_and_communities WMF strategic goal of Knowledge as a Service]
#Improve the visibility of MediaWiki usage by third-parties
#Spread awareness of '''commercial support''', regulatory certifications, and distributions (e.g. [https://www.mediawiki.org/wiki/BlueSpice BlueSpice])
#Recruit new organizations to adopt MediaWiki as a platform for enterprise knowledge
#Increase skills for existing editors, administrators, consultants and support organizations
#Recruit maintainers and contributors to extensions that are crucial to organizational use outside of WMF
#Add or improve content available at mediawiki.org
#'''Provide quality videos of the conference''' which may be shared, re-used and built upon.

==Project Plan==


===Activities===
#What is the purpose of the meeting and why is it important to your community?
#:Discuss current usage, trends, gaps, opportunities and challenges of using MediaWiki compared to other knowledge platforms
#If applicable, what benefits have you seen from doing this kind of meeting in the past?
#:Greater understanding of how MediaWiki is, and can be, used as a knowledge platform in intranet environments; Examine high profile MediaWiki deployments such as NASA's EVA Wiki Surface tools, resources, techniques and best practices for wikis in organizations large and small. Provide visibility into how organizations cope with the specific challenges of creating, nurturing and succeeding with their wiki projects.
#How will you let participants know about the meeting?
#:We've made repeated announcements on several WMF mailing lists, social media, and the [https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2019 Semantic MediaWiki site]
#How will you keep participants engaged after the meeting is over?
#:MWStake holds open meetings on a monthly basis. We update information at [https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group mediawiki.org] and https://mwstake.org We also have a slack channel
#Is there anything else you want to tell us about this project?
#:Hosting these videos on archive.org, commons, YouTube, Vimeo and other sites will give better visibility into how the MediaWiki software product can empower and engage people around the world to collect and develop knowledge resources. With professional quality video, the professional image of the product is improved.

===Impact===
How will you know if the project is successful and you've met your goals? Please include the following targets and feel free to add more:
#Number of total participants: approx 40-50 with unlimited video reach
#Number of people who will help organize the event: Organizing committee of five

===Resources===
''What resources do you have? Include information on who is organizing the project, what they will do, and if you will receive support from anywhere else (in-kind donations or additional funding).''
:[[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]] member [[MW:User:LexSMW|Lex Sulzer]] is the program chair (but has been taking on the bulk of the general chair) along with [[MW:User:AMagnien2|Airy Magnien]] ([https://uic.org/ UIC]), and [[MW:User:ClemFlip|Clément Flipo]].

''What resources do you need? For your funding request, list bullet points for each expense and include a total amount.''
* €950.40 ($1,047.62) - Video Equipment Rental
* €1,049.60 ($1,156.97) - Video Production Service
* €400.00 ($440.92) - VAT (Value Added Tax)
*: Note: The total, €2,400.00 ($2,645.21), is above the rapid grant max ($2,000), however the overage is projected to nearly be covered by conference attendees.

== Endorsements ==
''Community members are encouraged to endorse your project request here!''

:


[[Category:Rapid/Proposals/Video campaigns]]

Grants:Project/Rapid/SMWConFall2019/Video

2019-09-09T17:13:00Z

Bryandamon: Created page with "<div style="float:right; width: 24em"> {{Probox <!--When you are ready to submit your proposal for review, please change the status below to "proposed" and email rapidgrants@w..."

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= bryandamon{{@}}gmail.com

|project= MWStake/SMWCon2019Video

|affiliate= MW-SG

|summary= Provide funds for professional video production of the [https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2019 SMWCon Fall 2019] in Paris, France

|target= Third-party users, developers, and contribution to the MediaWiki product.

|start_date= September 25th

|start_year= 2019

|end_date= September 27th

|end_year= 2019

|amount_local= €1,813

|amount= $2,000

|grant_type= Group

|organization= [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]]

|contact2=

|website= [[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]]

|nonprofit= We are finalizing out non-profit status with the IRS now. If the grant is accepted and can't be given to MWStake until the non-profit status is achieved, it can be given to the conference organizers Clément Flipo or Lex Sulzer.

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>

*Please see the sample [[Grants:Project/Rapid/Plan/SampleApplication/Video campaigns|Video campaign application]] before drafting your application.
*You can also read a recent video campaign application, [[Grants:IdeaLab/Promotion_Of_Punjabi_Wikipedia_On_Social_Media|Promotion of Punjabi Wikipedia on Social Media]] and their [[Grants:IdeaLab/Promotion_Of_Punjabi_Wikipedia_On_Social_Media/Report|related report]].

==Project Goal==
#Hold a three-day conference featuring discussions of topics related to "Enterprise MediaWiki", i.e. the usage of MediaWiki software by and within companies, non-profits, governments, and other organizations.
#Further the [https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Direction#Knowledge_as_a_service:_A_platform_that_serves_open_knowledge_to_the_world_across_interfaces_and_communities WMF strategic goal of Knowledge as a Service]
#Improve the visibility of MediaWiki usage by third-parties
#Spread awareness of '''commercial support''', regulatory certifications, and distributions (e.g. [https://www.mediawiki.org/wiki/BlueSpice BlueSpice])
#Recruit new organizations to adopt MediaWiki as a platform for enterprise knowledge
#Increase skills for existing editors, administrators, consultants and support organizations
#Recruit maintainers and contributors to extensions that are crucial to organizational use outside of WMF
#Add or improve content available at mediawiki.org
#'''Provide quality videos of the conference''' which may be shared, re-used and built upon.

==Project Plan==


===Activities===
#What is the purpose of the meeting and why is it important to your community?
#:Discuss current usage, trends, gaps, opportunities and challenges of using MediaWiki compared to other knowledge platforms
#If applicable, what benefits have you seen from doing this kind of meeting in the past?
#:Greater understanding of how MediaWiki is, and can be, used as a knowledge platform in intranet environments; Examine high profile MediaWiki deployments such as NASA's EVA Wiki Surface tools, resources, techniques and best practices for wikis in organizations large and small. Provide visibility into how organizations cope with the specific challenges of creating, nurturing and succeeding with their wiki projects.
#How will you let participants know about the meeting?
#:We've made repeated announcements on several WMF mailing lists, social media, and the [https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2019 Semantic MediaWiki site]
#How will you keep participants engaged after the meeting is over?
#:MWStake holds open meetings on a monthly basis. We update information at [https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group mediawiki.org] and https://mwstake.org We also have a slack channel
#Is there anything else you want to tell us about this project?
#:Hosting these videos on archive.org, commons, YouTube, Vimeo and other sites will give better visibility into how the MediaWiki software product can empower and engage people around the world to collect and develop knowledge resources. With professional quality video, the professional image of the product is improved.

===Impact===
How will you know if the project is successful and you've met your goals? Please include the following targets and feel free to add more:
#Number of total participants: approx 40-50 with unlimited video reach
#Number of people who will help organize the event: Organizing committee of five

===Resources===
''What resources do you have? Include information on who is organizing the project, what they will do, and if you will receive support from anywhere else (in-kind donations or additional funding).''
:[[MW:MediaWiki Stakeholders' Group|MediaWiki Stakeholders' Group]] member [[MW:User:LexSMW|Lex Sulzer]] is the program chair (but has been taking on the bulk of the general chair) along with [[MW:User:AMagnien2|Airy Magnien]] ([https://uic.org/ UIC]), and [[MW:User:ClemFlip|Clément Flipo]].

''What resources do you need? For your funding request, list bullet points for each expense and include a total amount.''
* €950.40 ($1,047.62) - Video Equipment Rental
* €1,049.60 ($1,156.97) - Video Production Service
* €400.00 ($440.92) - VAT (Value Added Tax)
*: Note: The total, €2,400.00 ($2,645.21), is above the rapid grant max ($2,000), however the overage is projected to nearly be covered by conference attendees.

== Endorsements ==
''Community members are encouraged to endorse your project request here!''

:


[[Category:Rapid/Proposals/Video campaigns]]

Talk:Movement Strategy/Recommendations/Iteration 1/Product & Technology/7

2019-08-13T23:14:21Z

Bryandamon: Created page with "Thanks for starting this interesting conversation, after reading the recommendations, I have a few questions: * '''''We think there is a large third-party user base potential..."

Thanks for starting this interesting conversation, after reading the recommendations, I have a few questions:
* '''''We think there is a large third-party user base potential that is not currently realized ... (money, staff and volunteer time, brand and marketing, etc.)'''''
* '''''Improving our platform ties down a significant fraction of our budget, and even so the rate of progress is much slower than we’d like. If there is an opportunity to resource platform improvements in from external sources, we should take it.'''''
*: Isn't there already a decent "external" developer community? While the 3rd party ecosystem may not contribute monetarily (besides individual contributions), doesn't the Foundation get code support? How would the 3rd parties help with brand and marketing (aside from consultants/developers/hosts/etc. with branding for their own businesses)?
* '''''Becoming the essential infrastructure of free knowledge'''''
*: If the foundation really wanted to do this (platform for the world's free knowledge), they should really consider supporting [[WikiJournal|WikiJournal's proposal to become a full sister site]]
* '''''The theory that the MediaWiki ecosystem has significant third-party potential should be confirmed by research or small-scale experiments with early involvement of third parties, before a major investment is made. The risk of fallout between major stakeholders is expected to be both unlikely and low-impact, as long as the trademark and core development infrastructure is owned by Wikimedia.'''''
*: Doesn't [https://wikiapiary.com/wiki/Main_Page Wikiapiary] and [[mw:Manual:$wgPingback|$wgPingback]] provide a compelling case that there is a robust MediaWiki ecosystem? Not sure what changes might effect major stakeholders (or who they are? 3rd party users?), but it would seem there would be potential for a huge backlash if there were some breaking changes.
: --[[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 23:13, 13 August 2019 (UTC)

Proposal: WikiJournal as a sister project

2019-06-04T07:56:55Z

Bryandamon: Minor spelling (submitted & function)

{{WikiJ top menu}}

{{DISPLAYTITLE:<span style="font-family:Century Gothic, Helvetica, sans serif">{{FULLPAGENAME}}</span>}}
{{New sister project proposal
| status = discussion
| project_name = WikiJournal
| tagline = Open-access peer-reviewed academic journals with no publication costs.
| project_description = A site where authors can write their works directly online. The works then undergo independent scholarly peer review before being officially published in the journal.

Currently hosted in Wikiversity: '''[[WikiJournal User Group]]''', with the three journals ''[[v:WikiJournal of Medicine|WikiJournal of Medicine]]'', ''[[v:WikiJournal of Science|WikiJournal of Science]]'', and ''[[v:WikiJournal of Humanities|WikiJournal of Humanities]]''.

It is a way of bridging the Wikipedia–academia gap by enabling academics, scholars and professionals to contribute expert knowledge to the Wikimedia movement in the familiar academic publishing format that directly rewards scholars with citable publications. Initial [[wikiversity:WikiJournal_User_Group/Publishing|publishing formats]] include: Reviews (many integrated into Wikipedia), Original research, Case studies, Images/galleries.

''See also:'' [[v:WikiJournal_User_Group|General landing page]] {{!}} [[v:WikiJournal of Medicine/About|About Wiki.J.Med.]] {{!}} [[v:WikiJournal of Science/About|About Wiki.J.Sci.]] {{!}} [[v:WikiJournal of Humanities/About|About Wiki.J.Hum.]]
| multilingual_wiki = Many language versions
| multilingual = Initially English, eventually many
| technical_reqs = A number of unique features will be useful:
* It should be possible to categorize users as authors, editors, and/or peer reviewers.
* Separate namespaces for articles yet to be peer-reviewed, equivalent to Wikipedia's [[en:Wikipedia:Drafts|Draftspace]], e.g. Draft: or Preprint: or equivalent. (Currently stored in [[:v:Category:Pre-prints_not_yet_included_in_WikiJournal_of_Medicine|category]] and as [[v:WikiJournal_of_Science/Submissions|list]])
* Some way of automatically numbering figures with <nowiki>[[file:...]]</nowiki> formatting (currently done in the <nowiki>{{</nowiki>[[v:template:fig|fig]]<nowiki>}}</nowiki> template).
**VisualEditor-compatible insertion of cross-references to figures
* It is important to have the option not to make certain pages publicly accessible (i.e., viewable by only author and editors). This avoids violating press embargos for unpublished articles and allows re-submission to other journals if rejected by WikiJournal. (Currently, confidential works must be emailed to {{nospam|submissions|wikijmed.org}}).
* Preferably there should be an option to have restricted viewer access to some files, discussions, and user identities (e.g., anonymous peer-reviewers).
* Simple on-wiki forms for users with no wikimarkup experience, and automated editing post-wiki (currently handled with google docs)
** submission of [[wikiversity:WikiJournal_User_Group/Potential_upcoming_articles|articles ready for review]]
** submission of [[wikiversity:WikiJournal_User_Group/Peer_reviewers|peer reviewer comments]]
* Automated features based on wikidata and/or bots
** synchronisation of [[v:template:article info|article info template]] on main and talk pages
** of the [[v:WikiJournal_of_Science/Potential_upcoming_articles|tracking sheets]] when reviewer comments submitted
** [[wikiversity:WikiJournal_User_Group/Editorial_guidelines#Inclusion_of_approved_articles|metadata-submission to crossref]] of accepted articles
** addition of accepted articles to the current volume&issue
** XML annotation of articles in the [[:en:Journal_Article_Tag_Suite|JATS format]]
** addition of published articles into Wikidata
** transclusion/import/export with Wikipedia
** formatting of accepted articles into a specific PDF format (currently done manually via copy-paste to a [https://drive.google.com/file/d/0B4LQzkvkbO9YbEM5dktUUktTVlk/view DOCX template], which is then saved as a PDF. Another option could be to use the WikiMedia infrastructure as a [[w:Educational_Content_Sink|content sink]] and generate on demand other formats like docx, odt, LaTeX from the wiki syntax (e.g. via [http://www.pandoc.org PanDoc] or [[mw:Reading/Web/PDF_Functionality|MediaWiki PDF-export function]]). Requires e.g. two-column layout, inject logos, header styles etc. Manual tweaking of automated starting produced pdf would be ideal. Synchronisation to the latest version of the article would be ideal.
* Ideally we would like converters ''to'' wiki from DOCX and LaTeX so that articles can be more easily [[v:WikiJournal Preprints|submitted]].
* Specific left menu items
* Specific title fonts

| url =
'''Current''': hosted within Wikiversity links from:
*[http://Www.wikijmed.org www.wikijmed.org]
*[http://www.wikijsci.org www.wikijsci.org]
*[http://www.wikijhum.org www.wikijhum.org]
'''Ideal''': wikijournal.org (currently used for a separate start-up project by [[User:Fokebox]])<br>
'''Alternatively''': wikijournals.org, journal.wiki.org or journal.wikimedia.org
| logo = [[File:WikiJournal logo (flat blue yellow).svg|200px]]
Proposed logo matches current WMF sister project styles uses [https://trello.com/c/IRqbu8p4/15-color-swatches 2014 WMF colour palette]
<br>[[File:WikiJournal logo.svg|80px]] [[file:WikiJournal of Medicine logo.svg|80px]] [[file:WikiJournal of Science logo.svg|80px]] [[file:WikiJournal of Humanities logo.svg|80px]] [[file:WikiJournal Preprints logo.svg|80px]]
<br>Current logos of user group and specific journals within the group
<br>[[file:WikiJournal logo (flat black).svg|80px]] [[file:WikiJournal of Medicine logo (flat black).svg|80px]] [[file:WikiJournal of Science logo (flat black).svg|80px]] [[file:WikiJournal of Humanities logo (flat black).svg|80px]] [[file:WikiJournal Preprints logo (flat black).svg|80px]]
<br>Flat black version for small icons (including specific journals)

| more_settings =
| development_wiki = Not yet any separate technical-development wiki (e.g. in Wikimedia Labs)
| participants = Participants (editors, authors and peer reviewers) as of 2019-05-15
*'''Authors''': 172 ([[v:Template:Author_count|counting template]])
*'''Editorial boards'''': 62 ([[v:Template:Editor_count|counting template]])
*'''Associate editors''': 15 ([[v:Template:Editor_count|counting template]])
*'''Peer reviewers''': 70
*'''Additional on-wiki participants''': approx 5-10
'''Total''': approx 300-350
<br>[[Wikiversity:WikiJournal_User_Group/Editors|Editorial boards and associate editors]]
<br>[[WikiJournal_User_Group#Members_of_the_administrative_board|WikiJournal Admin board]]

Estimate of editors active in any given month:
*≥5 edits per month on-wiki: 25
*≥5 email to mailing lists: 25
*Monthly conference call meeting: 10
Notes: 1) a lot of work currently has to be done off-wiki. 2) Almost all peer reviewers only ever contribute once. 3) Many authors also only contribute once when depositing an article and once when responding to respond reviewer comments.

Readership from DOI-clicks in line with typical academic journals (800 per article).
{{Graph:Chart
| type = line
| width = 400
| height = 150
| xAxisTitle = 2018
| yAxisTitle = DOI resolutions per month
| x = Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov
| y = 1283,1312,1528,1289,1554,1970,1878,2036,4154,7780,12270
}}
}}

==Scenario==

# Many Wikipedia articles lack information (especially on complex topics)
#*Although [[w:wp:GA|GA]] and [[w:wp:FA|FA]] involve editorial review of content, there is little formal review from outside experts
#*Lack of quality images
#Lack of contributions from academic community
#*Wikipedia is often viewed with suspicion by academics
#*Academic authors often seek more recognition than provided in the history tab
#*Writing in Wikipedia is sufficiently unfamiliar to be a deterrent
#*Original research cannot be published on Wikipedia

==Possible solution==
The Wikipedia community and the academic community can be converged and unified through a journal initiative under the Wikimedia banner. The journals needs to adhere to international guidelines and standard procedures, in addition to being open-access and editable by all. WikiJournal can provide a prototype based on which journals for various themes and subjects can be built on.

This involves two broad aspects: The background structure and the journal contents.

===Background structure===
Background structure comprises:
* Journal policies: This can be customized based on the journal theme and subject, but would be common overall.
* Templates: Specific templates need to be designed for each journal. These templates would probably not be relevant to any other wikiproject.
* Technical parameters:
** Unlike other wikiprojects, the journal project calls for specialized logins as authors, editors and/or peer reviewers.
** We need to consider the possibility of one individual having multiple capacities, and the specific capacity being specified for an edit.
** Custom PDF-rendering facility.
** Possible on-wiki storage of confidential information (e.g. anon peer-reviewer identities).

===Journal contents===
* Anyone would be able to make a submission. Specification of legal name and contact details might be required.
* The submitted preprint contents would undergo a public peer-review by external experts and considered critically by an elected aditorial board before accepted into a journal's mainspace, or rejected.
* After acceptance, the editing capacities for the article would be restricted.
* A permalink in the form of [[W:Digital Object Identifier|Digital Object Identifier]] or DOI would be awarded to each article after publication.
* A citation format for academic publications would be specified.

==Present situation==
Three journals are currently published by the [[v:WikiJournal User Group|WikiJournal Publishing Group]]:

* [[v:WikiJournal of Medicine|''WikiJournal of Medicine'']] (est. 2014) for medicine and biomedicine (ISSN 2002-4436)
* [[v:WikiJournal of Science|''WikiJournal of Science'']] (est. 2018) for science, technology, engineering and mathematics (ISSN: 2470-6345)
* [[v:WikiJournal of Humanities|''WikiJournal of Humanities'']] (est. 2018) for humanities, arts, and social sciences (ISSN: 2639-5347)

WikiJMed was the original WikiJournal, and was the template for the subsequently established journals with broader scope (further info at [[v:WikiJournal of Medicine/About|WikiJournal of Medicine/About]]). Based on this initiative, WikiJSci (previously "Second Journal of Science") was developed in 2018 and was soon followed by WikiJHum. A composite [[WikiJournal User Group]] was formed in 2016 to overlook the development of such journals.

==Proposal==
A wiki that is open for everyone to contribute, at the same time with the features of scholarly journals in that the published works undergo independent peer-review by subject experts before publication. The authors are clearly credited at the top of their articles, making it more attractive for researchers and scholars to contribute. Articles are indexed and citable. Works may include images and reviews that are supported by secondary sources. Wikipedia and other Wikimedia sister projects can subsequently use material from these publications.

===Why separate Wikiproject===

* An internal [[Wikiversity:WikiJournal/Future as separate Wikimedia project|discussion]] revealed a consensus for a move to a separate Wikiproject.
* It calls for custom structure that would probably not be required by other Wikiprojects.
** Certain types of users would need to specify their real names and contact details.
** Login types might need to be specified.
** Custom templates.
* Better visibility and awareness. The current journals have limited viewership possibly due to lack of awareness across Wikimedia users.
* Grant requirements would follow a definite prototype.
* The scope is unique. This uniqueness needs to be identified.
** A separate link as another sister project will enhance its visibility to Wikimedia users would therefore enhance participation and impact.
* The scope does not exactly merge with:
** Wikiversity: Although there is partial overlap in relation to ''open research'', the scope of WikiJournal goes beyond that. ''Academic publications'' are not necessarily same as ''open academia'', ''open educational resources'' or ''learning projects''.
** Wikibooks: ''Academic publications'' are not necessarily same as ''open-content textbooks''.
** Wikipedia: Although Wikipedia is most read information source, it is often not given the credibility it deserves. While a few journals have started taking Wikipedia seriously, it still cannot claim the academic recognition that WikiJournal could claim.
* Impact metrics may not be applicable to any other wikiproject and may call for additional support from Wikimedia labs.
* Translation to other language wikis would call for standard protocols, unlike any other sister project.
* It is essential for journals to be enlisted in various databases and to follow various international protocols. A single repository for all such journals will help in minimising the problems of separate listing in such databases or central bodies.
* Established academic journals may set up spaces within such a project to implement similar reviews.

==Alternative proposals==
{{cot|Former proposals with similar scope|align=left|bg=#DDDDEE|border=0px|indent=10px;width:80%}}
*[[Wiki Scholarly Journals]]
*[[Wikiversity:Wikiversity:Journal of the future|Wikiversity:Journal of the future]]
*[[Wikisource:Wikisource:WikiProject Academic Papers|Wikisource:WikiProject Academic Papers]]
*[[Wikiversity:Wiki Journal]]
*[[Wikiversity:Portal:Wiki Scholar]]
*[[wikiversity:User:OpenScientist/Open_grant_writing/Encyclopaedia_of_original_research|Wikiversity:Encyclopaedia of original research]]
*[[strategy:Proposal:Journal_(A_peer-review_journal_to_allow/encourage_academics_to_write_Wikipedia_articles)|WikiStrategy:Journal]]
*[[Wikipedia Scientific Journal]]
{{cob}}
{{cot|Articles that mention the format|align=left|bg=#DDDDEE|border=0px|indent=10px;width:80%}}
* {{cite journal|last1=Masukume|first1=G|last2=Kipersztok|first2=L|last3=Das|first3=D|last4=Shafee|first4=T|last5=Laurent|first5=M|last6=Heilman|first6=J|title=Medical journals and Wikipedia: a global health matter|journal=The Lancet Global Health|date=November 2016|volume=4|issue=11|pages=e791|doi=10.1016/S2214-109X(16)30254-6|url=https://www.thelancet.com/journals/langlo/article/PIIS2214-109X(16)30254-6/fulltext}}
* {{Cite journal|last=Shafee|first=T|last2=Mietchen|first2=D|last3=Su|first3=A|date=August 2017|title=Academics can help shape Wikipedia|url=http://science.sciencemag.org/content/357/6351/557.2|journal=Science|volume=357|issue=6351|pages=557–558|doi=10.1126/science.aao0462}}
* {{Cite journal|last=Shafee|first=T|last2=Masukume|first2=G|last3=Kipersztok|first3=L|last4=Das|first4=D|last5=Häggström|first5=M|last6=Heilman|first6=J|date= August 2017|title=Evolution of Wikipedia’s medical content: past, present and future|url=http://jech.bmj.com/content/early/2017/08/24/jech-2016-208601|journal=JECH|doi=10.1136/jech-2016-208601|pmid=28847845}}
* {{Cite journal|url=https://www.hlinc.org.au/content/open-access/item/wikipedia-integrated-publishing-a-comparison-of-successful-models|title=Health Libraries - Wikipedia-integrated publishing: a comparison of successful models|publisher=Health inform.|volume=26 |issue=2|doi=10.13140/RG.2.2.27470.77129}}
* {{Cite journal|year=2017|title=WikiJournal of Medicine, the first Wikipedia-integrated academic journal|url=https://en.wikiversity.org/wiki/WikiJournal_of_Medicine/WikiJournal_of_Medicine,_the_first_Wikipedia-integrated_academic_journal|journal=WikiJournal of Medicine|volume=4|pages=|doi=10.15347/wjm/2017.001|last=Shafee|first =T|last2=Das|first2=D|last3=Masukume|first3=G|last4= Häggström|first4=M}}
* {{Cite journal|last=WikiJSci Editorial board|date=2018-06-01|title=The aims and scope of WikiJournal of Science|url=https://en.wikiversity.org/wiki/WikiJournal_of_Science/The_aims_and_scope_of_WikiJournal_of_Science|journal=WikiJournal of Science|language=en|volume=1|issue=1|pages=1|doi=10.15347/wjs/2018.001}}
{{cob}}
=== WikiJournal as a publishing house ===
'''WikiJournal as a publishing house''' I am a little confused about how a WikiJournal project would work: would other users be allowed to come along and edit already published research? Would it be like [http://www.scholarpedia.org/article/Main_Page Scholarpedia] where you need credentials? Rather than make a separate ''project'' as such, maybe "WikiJournal" could be a regularly-published periodical or a publishing imprint that has stable versions of articles that have been collaborated on at Wikiversity. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 18:13, 28 August 2016 (UTC)
:As summarized at [[Wikiversity:WikiJournal_of_Medicine/About#Structure|the structure of WikiJournal of Medicine]], anyone may edit pages, even published ones, but substantial edits to the main text of such articles would be reverted. Instead, users should then make a separate draft, and have that draft peer reviewed as well. Peer reviewers must be experts in the subject, but authors do not necessarily have to be. Collaborations at any site with a permitting license may be submitted. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 19:16, 2 September 2016 (UTC)

=== WikiJournal Public-Private-Versioning and Dynamic Paper Management in a Wiki ===
For a Journal the concept of '''[[Wikiversity:Public-Private-Versioning|Public-Private-Versioning]]''' could be used to facilitate a community based paper development (the community could contribute during the evolution of the paper - transparent history of the evolution of the paper, and private versions are created by a reviewing process (see [http://at6fui.weebly.com/open-community-approach.html Open Community Approach]).

Furthermore a KnitR-Backend or SageMath-Backend for Wikiversity papers can be used for statistical and/or numerical analysis of data for the paper (see '''[https://en.wikiversity.org/wiki/KnitR#Workflow_for_KnitR-Backend_for_in_Wikiversity.2FWikipedia KnitR in Wikiversity]''').
--[[User:Bert Niehaus|Bert Niehaus]] ([[User talk:Bert Niehaus|talk]]) 15:11, 11 August 2017 (UTC)
:Apologies for the delayed reply! I think the project would need some feedback on the best overall architecture to use behind the scenes (what can be done directly with mediawiki, and what can be third-party) so long as they interface well. One limitation we've had, for example, is that reviewers have to submit comments via a google form because there is not yet visualeditor in talkpages, and anonymous editors need to privately register their identity and affiliation with the editorial board. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 06:19, 1 June 2019 (UTC)

== Discussion ==

#{{Support}}. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 18:18, 21 August 2016 (UTC) Editor-in-chief, WikiJournal of Medicine
#'''Disagree with split''' I don't see why it's valuable to split this from WV--this is perfectly within its scope. In fact, it is one of the real triumphs of that project and splitting it off would probably be to the detriment of that site. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 21:52, 21 August 2016 (UTC)
#: Having Wikiversity lose WikiJournal might be a huge loss to you, [[User:Koavf|Justin]]. However, all's not lost for Wikiversity, and there is still hope for Wikiversity. Indeed, Wikiversity has English courses, like [[v:English as a second language]], most of which needs further improvements. Recently, I had to help one of users who utilized his <u>poor</u> English writing skills at English Wikipedia. To help him improve his English skills, I had to direct him to [[v:English]] and [[b:English]]. I received thanks for helping him. Therefore, Wikiversity may be needed for users who want to improve their English writing skills for English Wikipedia. Don't you think so? --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 05:44, 26 June 2017 (UTC); edited, 05:54, 26 June 2017 (UTC)
#::{{Ping|George Ho}} Honestly, it seems like your English is better in the months that I've seen you posting across WMF sites. I definitely believe that there is potential in Wikiversity but I just don't think this should split from it. We'll see how it goes. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 05:50, 26 June 2017 (UTC)
#::: Thanks for complimenting my English. ;) --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 05:54, 26 June 2017 (UTC)
#{{Support}} A journal needs specific tools. Having it as its own sister site would be ideal. [[User:Doc James|<span style="color:#0000f1">'''Doc James'''</span>]] ([[User talk:Doc James|talk]] · [[Special:Contributions/Doc James|contribs]] · [[Special:EmailUser/Doc James|email]]) 15:00, 22 August 2016 (UTC)
#::I continue to '''strongly support''' this project. This is an effective method of bringing in knowledge to our movement. This may also have potential for oral knowledge from indigenous peoples with a less robust publishing tradition.[[User:Doc James|<span style="color:#0000f1">'''Doc James'''</span>]] ([[User talk:Doc James|talk]] · [[Special:Contributions/Doc James|contribs]] · [[Special:EmailUser/Doc James|email]]) 11:24, 3 June 2019 (UTC)
#{{Support}} Very promising proposal --[[User:Athikhun.suw|Athikhun.suw]] ([[User talk:Athikhun.suw|talk]]) 00:52, 28 August 2016 (UTC)
#{{Support}} I agree with the split. I don't think it belongs with Wikiversity at all, which is for courses and curricula. It makes more sense to me, if anything, that it should be part of Wikibooks, as that is a place for publication of original scientific works. The process for a journal paper is different than a book however so I agree it should be separate. As for the project in general, I think the wiki approach to writing a scientific paper is potentially really great. I know PLOS has their own internal wiki for writing [http://collections.plos.org/topic-pages Topic Pages], which are review papers that are written and then eventually transferred to Wikipedia. Non-review papers, however, don't really make sense as part of Wikipedia, so it makes sense to develop them on their own wiki. [[User:Mvolz|Mvolz]] ([[User talk:Mvolz|talk]]) 17:44, 30 August 2016 (UTC)
#{{Support}} (finally after changing my mind three times: I never oppose a reasonable request if it has the support of the community --[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 23:06, 3 June 2019 (UTC))<s> '''Disagree with split''' (''Changed vote to '''neutral''' with the understanding that the real question is whether the wiki hosts confidential or "private" conversations'') <small>Original text:</small> Keep in mind that I speaking from the biased perspective of a [[v:Wikiversity:Custodianship|Wikiversity Custodian]] who is only marginally involved with this WikiJournal project. One reason Wikiversity would want to host the journals is that the software developed for WikiJournal could be useful on Wikiversity. An example of such software might include confidential communications between editors and referees that are held on-wiki (instead of on a remote user group). I have no idea whether Wikimedia is willing or even able to host such confidentiality, but it would also allow students and authors to collaborate privately. Also, Wikiversity would be interested in hosting student-run journals. I concede that the prospect of amateaurish student-journals might not be appealing to board members, and fully understand why the board might wish to separate from Wikiversity. If the board chooses to split, I will support that decision.</s> --[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 01:35, 3 September 2016 (UTC)
#:Confidential talks are currently held on a [https://groups.google.com Google Group], which can be used for students and authors even if WikiJournal is split from Wikiversity. Likewise, students have at least the same ability to start journals after a split. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 12:57, 3 September 2016 (UTC)
#::Allowing for confidential conversations on a Wikimedia sister-wiki would be a major departure from protocol. The wiki that does it will need an independent governing body for each journal or organization that uses it. Someday, it would be nice for universities, laboratories, and journals to have such capabilities. I am neutral about the current proposed split if the confidentality is not included: Without the confidentiality option, I see neither a reason for the split, nor any harm done by splitting away from Wikiversity. But if this new wiki is created with confidentiality options, it will likely recruit university and laboratory-based journals that wish to utilize this option. The question of whether to allow this confidentiality option is likely to go to the top levels of the Wikimedia corporation...Perhaps what we really need is for Google groups to host discussions in wikitext.--[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 19:03, 3 September 2016 (UTC)
#::{{ping|Mikael Häggström}} The private option is already availablae at '''https://wikiversity.miraheze.org/wiki/Main_Page'''--[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 16:46, 4 September 2016 (UTC)
#{{Support}} The scope is unique and can extend to a number of domains. Specific tools needed. Access rights need to be different. It is also important to have the option of certain pages not being publicly accessible such that press embargo for unpublished articles do not get violated and yet editors or peer reviewers get to work in wiki format. <font face="Segoe script">[[User:Diptanshu Das|'''<font color="#ff0000">D</font><font color="#ff6600">ip</font><font color="#009900">ta</font><font color="#0000ff">ns</font><font color="#6600cc">hu</font>''']][[User talk:Diptanshu Das|<sup>Talk</sup>]]</font> 12:21, 5 September 2016 (UTC)
#{{Support}} I definitely agree with this. If it does air how would the three statutes you mentioned be done? Would peer reviewer, editor, and author have different edit rights or be purely decorative, and would you have to apply for them? [[User:Iazyges|Iazyges]] ([[User talk:Iazyges|talk]]) 04:55, 6 September 2016 (UTC)
#:Good questions, [[User:Iazyges|Iazyges]]. I see no reason for editors to need any particular edit rights, and readers without any account should be able to edit too, [[Wikiversity:WikiJournal_of_Medicine/Editors#Editing_published_works|even published works under certain conditions]]. I think the author role is also rather decorative, since it's the quality of their works that matter. I think the peer reviewers should need to apply, so that we know they fulfill [[Wikiversity:WikiJournal_of_Medicine/Peer_reviewers#Criteria|the criteria]]. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 18:55, 15 September 2016 (UTC)
#{{Support}} per DocJames--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 11:59, 6 September 2016 (UTC)
#{{Support}} Because an open access journal is very different from WV and WB. --[[User:Netha Hussain|Netha Hussain]] ([[User talk:Netha Hussain|talk]]) 09:03, 13 September 2016 (UTC)
#{{Support}} because I'm looking for a project like this to publish some ideas. --[[User:Sophivorus|Felipe]] ([[User talk:Sophivorus|talk]]) 16:29, 20 November 2016 (UTC)
#{{Support}} - If this happens, I can read well the promising journal articles by academics. Though I can't write well the stuff, I can be a good reader to this. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 22:20, 18 January 2017 (UTC)
#:{{comment|Belated post-vote comment}}: I recently read peer reviews on scholarly articles and was amazed by comments and responses. I am also intrigued by the peer review templates, like [[v:en:Template:editor's comments]] and [[v:en:Template:Response]]. I [https://en.wikiversity.org/w/index.php?title=Talk:Radiocarbon_dating&diff=prev&oldid=1787502 fixed] a usage error recently, so I wonder whether the project can adopt either the templates or some software similar to MediaWiki's Support Desk or something like Wikinews's Comments (like [[:n:en:Comments:Judge jails 'monstrous' London serial killer Stephen Port|this example]]). Honestly, I found the templates less convenient for peer reviews, so I figured that some discussion software would be a better improvement. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 09:34, 5 December 2017 (UTC)
#{{Support}} -[[User:Richard923888|Richard923888]] ([[User talk:Richard923888|talk]]) 15:39, 21 January 2017 (UTC)
#{{Support}} - there is no reason why a separate journal cannot continue to link with WV but there is immense potential that cannot be achieved by remaining a sub-project. <span style="color:#29AB87">[[User:Green Giant|Green Giant]]</span> ([[User talk:Green Giant|talk]]) 15:09, 15 April 2017 (UTC)
#{{Support}} - This proposal has evolved and improved significantly since first proposed in 2016. The flagship ''WikiJournal of Medicine'' exemplifies what the project can achieve (see [http://dx.doi.org/10.15347%2Fwjm%2F2017.001 2017 editorial]). Starting up within Wikiversity was useful to incubate the project and prove that such a novel format is even feasible. Becoming a sister project would further support the initiative by adding legitimacy, support, and extra control of sidebar contents etc. There would remain a strong focus on generation, improvement, peer-review and re-integration of high-quality content into other WMF projects (especially Wikipedia), and a WikiJournal sister project would maintain strong ties to the other projects. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 01:03, 18 April 2017 (UTC)
#:I should note for transparency that since my original support vote, I'm now Editor-in-Chief of WikiJournal of Science, and I chair the administration board. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 00:07, 4 June 2019 (UTC)
#{{Support}} Great proposal!--[[User:Kiril Simeonovski|Kiril Simeonovski]] ([[User talk:Kiril Simeonovski|talk]]) 06:52, 9 May 2017 (UTC)
#{{Support}} For reasons adequately described above. · · · [[User:Pbsouthwood|Peter (Southwood)]] [[User talk:Pbsouthwood|<sup>(talk)</sup>]]: 08:09, 9 May 2017 (UTC)
#{{Support}} Great proposal with value for the academic community. <b>~<i><font color="#07517C">[[User:SuperHamster|Super]]</font></i><font color="#6FA23B">[[User:SuperHamster|Hamster]]</font></b> <small>[[User talk:SuperHamster|Talk]] [[Special:Contributions/SuperHamster|Contribs]]</small> 17:00, 9 May 2017 (UTC)
#{{Support}} more than that it is exactly what i had in mind because the lack of open source credited material is recurrent fact on wikipedia and it will expand wikimedia scope. --[[Special:Contributions/167.63.49.24|167.63.49.24]] 02:52, 2 June 2017 (UTC)
#{{Support}} - Seems like a reasonable proposal, I don't see why it shouldn't at least be given a try. I think the challenge will mostly consist of getting experts in various fields to peer-review, but that's not impossible to do. [[User:InsaneHacker|InsaneHacker]] ([[User talk:InsaneHacker|talk]]) 06:27, 2 July 2017 (UTC)
#<s>{{oppose}} they don't need an entire sister project. It has to stay in [[v:|WV]].</s>this user voted 2x, therefore have struck one vote--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 15:29, 24 October 2017 (UTC)
#:{{strong oppose}} to separate login. Just add the obligation to fill an ''informations'' tab in ''Preferences'' to allow contributing [[User:CreativeC38|CreativeC38]] ([[User talk:CreativeC38|talk]]) 10:19, 6 July 2017 (UTC)
#::{{Ping|CreativeC38}} Why does it ''have'' to stay on WV? You don't think there's any merit whatsoever to having it as a separate site instead of a subpage on WV in terms of presentation, attracting experts etc.? [[User:InsaneHacker|InsaneHacker]] ([[User talk:InsaneHacker|talk]]) 00:24, 8 July 2017 (UTC)
#:: Also, the "oppose" and "strong oppose" vote [https://meta.wikimedia.org/w/index.php?title=WikiJournal&diff=16967843&oldid=16955738 are yours]. I'm informing readers to avoid misleads. BTW, sometimes you feel that Wikiversity won't be the same without WikiJournal. However, Wikiversity has been Wikiversity, especially without WikiJournal. Also, it has some good lessons for others to read, like [[v:English]]. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 03:48, 8 July 2017 (UTC)
#{{Support}} - I think it is to Wikiversity's detriment that WikiJournal find a separate home, however, it does seem to be a better approach for WikiJournal itself, and it should attract more users to the wiki community. I trust that WikiJournal will encourage academics to develop lessons and courses supporting their work at Wikiversity. -- [[User:Dave Braunschweig|Dave Braunschweig]] ([[User talk:Dave Braunschweig|talk]]) 21:49, 8 July 2017 (UTC)
#{{Support}} I think WikiJournal would have better chances to develop and to engage with expert communities if it were a sister project. --<font style="font-family:Monotype Corsiva; font-size:15px;"> [[User:Daniel Mietchen|Daniel Mietchen]] ([[User talk:Daniel Mietchen|talk]]) </font> 17:38, 31 August 2017 (UTC)
#{{Support}} I agree my previous speaker. Good point -- <span style="font-variant:small-caps">[[User:DerFussi|Der]][[User talk:DerFussi|Fussi]]</span> 06:12, 13 September 2017 (UTC)
#{{s}} Per others. -- [[User:Thennicke|Thennicke]] ([[User talk:Thennicke|talk]]) 23:23, 16 October 2017 (UTC)
#'''Comment''' I propose to lessen the requirement to first make the article available in wiki format. Consider my case: I wrote a book (i.e. a very long article) in PDF format (generated from LaTeX) with my original research in mathematics and make it publicly available under an open license. I have a trouble publishing it, because journals don't publish 380 pages articles and book publishers refuse to publish a book which is already available online. I want to allow me to submit the PDF file and be reviewed in WikiJournal project. Note that converting PDF into wiki markup would be a hard work, and this way it would be needed to update after each change in my book (e.g. when I add a solution of a conjecture or correct a typo). --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 23:44, 26 October 2017 (UTC)
#:{{re|VictorPorton}} We definitely hope to implement some easier ways of importing LaTeX, DOCX and PDF submissions on the [[v:WikiJournal Preprints|submissions page]]. That will likely require help from the WMF's dev team. Currently, the main conversion option is probably [http://pandoc.org Pandoc]. We have had people submit as docx files, and the journal editors have manually reformatted for wikimarkup, but that's not a scalable solution. Note that currently only Wiki.J.Med. is accepting original research, whist the other journals starting up are focusing on review articles (at least initially) since these are 'safer' options for building the journals early on. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 02:55, 27 October 2017 (UTC)
#::It seems that we will never (or at least in near 50 years) have a good automated conversion from LaTeX to wiki. I propose not to convert but to allow the author to upload a PDF file and publish in the wiki just a link to author's files, not the article itself in wiki markup. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 12:33, 27 October 2017 (UTC)
#::We also need some reasonable policy about updates of already published articles. For example arXiv allows to upload more than one version of an article. (This is especially important with articles building a theory rather than proving a single result.) We need it too. Probably every change should be peer reviewed. Or we can trust authors that they improve their materials over time not make it worse. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 12:39, 27 October 2017 (UTC)
#:::The downside of if we were to have only a pdf version and no wikimarkup version, is that it would make it hard to integrate material into other Wikimedia projects (one of the current main goals of the journals). However, this is not set in stone, so could change. As for multiple versions - I agree with the need for more specific guidelines (it happens not to have come up yet). In addition to the history tab record of all edits during drafting on the preprint server, my expectation is that anything that changes content of a published article would have to be re-reviewed to retain legitimacy. Indeed I can imagine that people could publish updated 'versions' of a review article, as already happens for textbooks. I'd suggest more in-depth discussion be on the main [[v:Talk:WikiJournal_User_Group|WikiJournal discussion page]]. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 13:51, 27 October 2017 (UTC)
#::::Anyway my book won't be completely copied to Wikipedia. So to convert the entire book and every its part into wiki markup format is just largely useless work. If we need to publish some part in a wiki, we can convert parts of the book or article on as-needed basis. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 22:03, 27 October 2017 (UTC)
#::::: Hello, [[User:VictorPorton|Victor]]. Here is [[v:en:WikiJournal Preprints]], which has instructions on sending PDF files via email and provides email address for those wanting to send PDF files. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 02:15, 29 October 2017 (UTC)
#{{Support}} This sounds like "a hidden gem 💎" situation where something good is hidden in something else, people who would be interested in this but otherwise not in the Wikiversity might be able to see this sooner if it weren't "hidden away". --[[User:Donald Trung|Donald Trung]] ([[User talk:Donald Trung|Talk 🤳🏻]]) ([[Steward requests/Global/2017-08#Global lock Donald Trung and sockpuppets|My global lock 😒🌏🔒]]) ([[Steward requests/Global/2017-09|My global unlock 😄🌏🔓]]) 11:44, 10 November 2017 (UTC)
#{{support}} Very important project. [[User:Ammarpad|Ammarpad]] ([[User talk:Ammarpad|talk]]) 14:45, 18 November 2017 (UTC)
#{{Support}} This proposal has a unique scope, and would have been the only WMF project to seem trustworthy for referencing by most of academics. In addition to the potential features listed on the top, this project would require much stricter internal procedures and hence Wikiversity does not fit in its current form. --[[User:Strange quark|Strange quark]] ([[User talk:Strange quark|talk]]) 13:30, 30 December 2017 (UTC)
#'''Support''' I'm ready to give a hand for french version of this sister project. [[User:Lionel Scheepmans|Lionel Scheepmans]] <sup><big>✉ </big> [[User talk:Lionel Scheepmans|Contact]]</sup> <sub>French native speaker, sorry for my [[w:dysorthography|dysorthography]]</sub> 20:28, 25 February 2018 (UTC)
#{{support}} [[User:NMaia|NMaia]] ([[User talk:NMaia|talk]]) 09:32, 26 March 2018 (UTC)
#'''question'''('''comment''') we have 26 signatures above plus journals which have been added[https://en.wikiversity.org/wiki/WikiJournal_of_Science] and [https://en.wikiversity.org/wiki/WikiJournal_of_Humanities] ...so where are we in terms of the process of this proposal?(how much longer)thank you--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 20:27, 11 September 2018 (UTC)
#*{{Re|Ozzie10aaaa}} yes, previously comment has been from people who happened to come across the page. The [[Sister Projects Committee#Current%20new%20project%20process|Sister Projects Committee]] suggested the gathering of contributor data and to make sure that people in different projects are aware of the proposal, so I have placed some notifications around a few areas in wikipedia, wikidata and mailing lists. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 09:31, 2 June 2019 (UTC)
#{{support}} [[User:Reboot01|Reboot01]] ([[User talk:Reboot01|talk]]) 13:47, April 25, 2019 (UTC)
#{{support}} Splitting it could really allow greater participation in WJ from outside stakeholders. [[User:StudiesWorld|StudiesWorld]] ([[User talk:StudiesWorld|talk]]) 10:20, 16 May 2019 (UTC)
#{{support}} interesting proposal and splitting can make the arrangements much better! '''--'''[[User:علاء |<font size="3" face="Script MT Bold" style="color:black;">Alaa</font> ]] [[User_talk:علاء |:)..!]] 04:29, 2 June 2019 (UTC)
#{{support}} as article author - (Michael Stear) [[Special:Contributions/131.172.248.203|131.172.248.203]] 04:30, 2 June 2019 (UTC) 
#{{support}} as article author - (Kholhring Lalchhandama) [[User:Chhandama|Chhandama]] ([[User talk:Chhandama|talk]]) 06:20, 2 June 2019 (UTC) 
#{{support}} - (Fiona Mackinnon) [[Special:Contributions/49.180.152.237|49.180.152.237]] 04:57, 2 June 2019 (UTC) 
#{{support}} - [[User:Learnerktm|Learnerktm]] ([[User talk:Learnerktm|talk]]) 06:23, 2 June 2019 (UTC) 
#{{support}} as article author - (Andrew Z. Colvin) [[User:Azcolvin429|Azcolvin429]] ([[User talk:Azcolvin429|talk]]) 06:35, 2 June 2019 (UTC) 
#{{support}} as article author - [[v:User:Tsirel|Boris Tsirelson]]. WikiJournal evidently is very different from (the rest of) Wikiversity. [[User:Tsirel|Tsirel]] ([[User talk:Tsirel|talk]]) 07:00, 2 June 2019 (UTC)
#{{support}} - as article author - other WV articles I've read have little to do with those of WJ. However, I can understand the concerns raised here[https://en.wikipedia.org/wiki/Wikipedia_talk:Featured_article_candidates#A_proposal_for_WikiJournals_to_become_a_new_sister_project]. [[User:Funk Monk|FunkMonk]] ([[User talk:FunkMonk|talk]]) 07:00, 2 June 2019 (UTC) 
#{{support}} as article author - (Abdulmutalab Musa) [[User:Laamiido|Laamiido]] ([[User talk:Laamiido|talk]]) 07:39, 2 June 2019 (UTC) 
# {{support}} as article reviewer - (Gregor Stiglic) [[Special:Contributions/100.8.28.171|100.8.28.171]] 10:18, 2 June 2019 (UTC) 
#{{support}} as article author - (Lauren Gawne) [[Special:Contributions/14.203.84.11|14.203.84.11]] 10:38, 2 June 2019 (UTC) 
#{{support}} as article author -(Ozzie Anis)--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 10:57, 2 June 2019 (UTC)
#{{support}} as article author - [[User:Andrew Dalby|Andrew Dalby]] ([[User talk:Andrew Dalby|talk]]) 11:15, 2 June 2019 (UTC)
#{{support}} as article author - I vote FOR WikiJournal to become a full 'Sister Project' of Wikipedia. (Deepesh Nagarajan) [[Special:Contributions/14.139.128.17|14.139.128.17]] 11:46, 2 June 2019 (UTC)
#{{support}} [[User:Dank|Dank]] ([[User talk:Dank|talk]]) 12:23, 2 June 2019 (UTC)
#{{s}} [[User:Richard Nevell|Richard Nevell]] ([[User talk:Richard Nevell|talk]]) 12:49, 2 June 2019 (UTC)
#{{support}} - [[User:FULBERT|FULBERT]] ([[User talk:FULBERT|talk]]) 13:02, 2 June 2019 (UTC) - For journals to be taken seriously as academic and peer-reviewed contributors to knowledge, they need to appear solid and independent. Wikiversity is a wonderful idea, though it is not as useful as a dedicated space for open, peer-reviewed journal work. I believe that having a dedicated project space may also allow for some dedicated resources and visibility. This is consistent with the Wikimedia strategy to become the essential infrastructure of the ecosystem of free knowledge through knowledge as a service and knowledge equity.
#{{support}} as article reviewer - Niclas Borinder [[Special:Contributions/81.227.107.149|81.227.107.149]] 13:37, 2 June 2019 (UTC)
#{{support}} We have some details to sort but yes, for the spirit of it all and for committing significant resources to advance this idea in the immediate future, I support. [[User:Bluerasberry|<span style="background:#cedff2;color:#11e">''' Blue Rasberry '''</span>]][[User talk:Bluerasberry|<span style="background:#cedff2;color:#11e">(talk)</span>]] 14:10, 2 June 2019 (UTC)
#{{support}} as article author - Dudley Miles. I have found the project valuable in getting reviews by academic experts to raise the standard of an article. [[User:Dudley Miles|Dudley Miles]] ([[User talk:Dudley Miles|talk]]) 14:18, 2 June 2019 (UTC)
#{{support}} - [[User:Jacknunn|Jacknunn]] ([[User talk:Jacknunn|talk]]) 14:30, 2 June 2019 (UTC) This project has huge potential to bring peer-review to Wikipedia and have clear integration into the most famous Wikimedia project. Wikiversity has huge potential - but to speak frankly, it is not a University- The Open University is, and was very ahead of its time and one day, Wikimedia might partner or create something similar under this name. For now, it is not a University, and so is confusing to people not intimately familiar with Wikimedia projects (99.9999% of humanity). Even if it were a proper University, most universities create separate affiliated publishing houses (https://en.wikipedia.org/wiki/List_of_university_presses). I think simplifying this project as much as possible - that is 'creating peer-reviewed Wikimedia content using the familiar publishing norms of established peer-reviewed journals' is a good start, one that Wikimedia can build on and improve in alignment with the founding principles of the foundation. Project S is coming, let's be ready to meet it with a great front end and and even better back one! :)
#{{support}} Thank you for this well thought-out proposal, which addresses many limitations that have been identified over the course of the last few years. There are great benefits in separate sister project status, and honestly I don't think WV is a very suitable place for the journals to remain at at this point. --[[User:Elmidae|Elmidae]] ([[User talk:Elmidae|talk]]) 14:40, 2 June 2019 (UTC)
#{{oppose}} Various "technical requirements" violate the [[Founding principles]], especially the second one. While I understand the reasons, I don't think that such a project should be part of the Wikimedia "wiki family"; academic publishing works primarily through the reputation of its authors and publishers while Wikimedia projects work mostly on the basis of the dedicated interest of number of editors (both casual, sporadic, one time and regular ones) irrespective of their qualifications and trying to put both of them together isn't going to work due to the culture contrast. [[User:Jo-Jo Eumerus|Jo-Jo Eumerus]] ([[User talk:Jo-Jo Eumerus|talk]], [[Special:CentralAuth/Jo-Jo Eumerus|contributions]]) 15:18, 2 June 2019 (UTC)
#*that 'culture contrast' has existed for many years, a journal of this nature would only be a positive...IMO--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 16:12, 2 June 2019 (UTC)
#*:Yeah, and we've had problems with it. I don't disagree with the existence of such a project, I object to making it part of the Wikimedia family. [[User:Jo-Jo Eumerus|Jo-Jo Eumerus]] ([[User talk:Jo-Jo Eumerus|talk]], [[Special:CentralAuth/Jo-Jo Eumerus|contributions]]) 16:25, 2 June 2019 (UTC)
#{{oppose}}, per Jo-Jo Eumerus. - [[User:SchroCat|SchroCat]] ([[User talk:SchroCat|talk]]) 16:00, 2 June 2019 (UTC)
#{{support}} as article reviewer - Jennifer Dawson [[User:JenOttawa|JenOttawa]] ([[User talk:JenOttawa|talk]]) 16:05, 2 June 2019 (UTC) 
#{{support}} as a Wikijournal contributor. One of the reasons I support this is that a journal would let us go farther than writing for an encyclopedia. Often, Wikipedia policies such as [https://en.wikipedia.org/wiki/Wikipedia:No_original_research NOR (no original research)] hinders our ability to be academic. For example, the article I was honored to submit, [https://en.wikiversity.org/wiki/WikiJournal_of_Humanities/Themes_in_Maya_Angelou%27s_autobiographies Themes in Maya Angelou's autobiographies], isn't comprehensive because there are no sources to fill in some aspects of the topic. Although I'm not an academic expert, my experience as a WP editor of this article and others like it has made me into an expert about Dr. Angelou. I'd like to see the mission of the Wikijournal expand to allow original research, in order to expand the comprehensiveness of topics. In that way, we can improve upon the academic nature of WP and fill in the gaps imposed upon us by WP policies and procedures and the gaps that are out there in academic literature. [[User:Figureskatingfan|Figureskatingfan]] ([[User talk:Figureskatingfan|talk]]) 21:24, 2 June 2019 (UTC)
#::'''Comment''' Agree. The same problem with Wikipedia in the (quite far) topic - mathematics. Wikipedia's principle is "to inform, not teach/explain", but readers really need explanations and examples, which often leads to violations of the "no original research" norm, and frustration on both sides, readers and editors. WikiJournal is able to complement Wikipedia with explanations and examples using expertise. For example, my recent submission (explanatory essay) "[[v:WikiJournal Preprints/Can each number be specified by a finite text?]]". Wikiversity admits original research, but does not restrict it by peer refereeing, which is a completely different story. [[User:Tsirel|Tsirel]] ([[User talk:Tsirel|talk]]) 05:24, 3 June 2019 (UTC)
#{{support}} - (Tseenster) [[User:Tseenster|Tseenster]] ([[User talk:Tseenster|talk]]) 23:43, 2 June 2019 (UTC) 
# {{oppose}} primarily per Jo-Jo Eumerus, with the added caveat that according to [[mw:Template:Page security extension disclaimer]], {{tq|MediaWiki was not written to provide per-page access restrictions, and almost all hacks or patches promising to add them will likely have flaws somewhere}}, meaning that the technical requirements violate not only founding principles but also the very way the code for MediaWiki is designed. [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">has returned</sub>]] 00:39, 3 June 2019 (UTC)
#{{support}} - [[User:Benoit Rochon|Benoit Rochon]] ([[User talk:Benoit Rochon|talk]]) 01:36, 3 June 2019 (UTC)
#{{support}} - as one of the few new projects that I have seen that makes sense. This one just fits. [[User:Philippe|--Philippe]] ([[User talk:Philippe|talk]]) 01:59, 3 June 2019 (UTC)
#{{support}} - Wade Kelly [[User:Mrkellar|Mrkellar]] ([[User talk:Mrkellar|talk]]) 06:00, 3 June 2019 (UTC) 
#{{support}} - Steven Chang [[User:Gixibyte|Gixibyte]] ([[User talk:Gixibyte|talk]]) 06:40, 3 June 2019 (UTC)
#{{support}} - [[User:Rwatson1955|Rwatson1955]] ([[User talk:Rwatson1955|talk]]) 07:27, 3 June 2019 (UTC) 
#{{support}} as article author - (Ignacio López) [[User:Munguira|Munguira]] ([[User talk:Munguira|talk]]) 08:04, 3 June 2019 (UTC) 
#{{support}} [[User:Mardetanha|<font face="Rage Italic" size="4" style="color:#000000;color:black"><i>Mardetanha</i></font>]] <sup><span style="font-family:Italic;color:black">[[user_talk:Mardetanha|talk]]</span></sup> 09:08, 3 June 2019 (UTC)
#{{s}}.--[[User:Vulphere|<span style="background:#000000; color:white; padding:2px;">Vulp</span>]][[User talk:Vulphere|<span style="background:#00b700; color:white; padding:2px;">here</span>]] 09:24, 3 June 2019 (UTC)
#{{support}} - (Niall O’Mara) [[User:Ngdomara|Ngdomara]] ([[User talk:Ngdomara|talk]]) 09:57, 3 June 2019 (UTC)  support
# {{support}} as article reviewer - Herbert Haller
# {{s}} - this project has a lot of potential and it makes sense to give it the resources it needs to grow. [[User:Sic19|Simon Cobb]] ([[User:Sic19|Sic19]] ; [[User_talk:Sic19|talk page]]) 13:34, 3 June 2019 (UTC)
#{{support}} - Amy Fountain [[User:AmyFou|AmyFou]] ([[User talk:AmyFou|talk]]) 14:31, 3 June 2019 (UTC) 
#{{support}} - Arfon Smith [[Special:Contributions/128.177.88.206|128.177.88.206]] 14:50, 3 June 2019 (UTC) 
#{{question}} – I assume any new journals are going to incubate within this project, right? (I don't see us being equipped at Incubator to get involved.) [[User:StevenJ81|StevenJ81]] ([[User talk:StevenJ81|talk]]) 17:08, 3 June 2019 (UTC)
#{{support}} - This is a solid proposal with a healthy ecosystem of participants. Full-discloure, my wife among them. :) Opposing this based upon technical requirements is a distraction. People use tools other than MediaWiki everyday to support the movement. If we could, I'd rather folks use an open-source solution than have their work buried in some closed-source system owned by for-profit company. Besides, [[Community_health_initiative/Partial_blocks|partial blocks exist in MediaWiki]] and extending that to other use cases is a strength of a flexible open-source platform. Not to get too into the weeds, but it's also commented as "preferred", not a do-or-die requirement for success. These are smart people and I'm sure they can get it done. :) So again, technical fiddly-bits are a weak argument to oppose and I'd rather see us make a strong argument to support a burgeoning new project. [[User:Ckoerner|Ckoerner]] ([[User talk:Ckoerner|talk]]) 17:51, 3 June 2019 (UTC)
#{{support}} Yes, I find it helpful that wikijournal is it's own project sort of like how wikiversity is it's own project and not included into wikibooks. Wikijournal is a complex process and the peer review process isn't easy for an open project to do, yes, enwikiversity did a great job but I guess with more specific structure, it will be more conducive for academics to review journals which then will allow more growth. For this structure, I will hope it can be developed with wikiversity in mind (in some sense like OTRS can be shared with all projects - the tool and etc). I find it more useful for wikiversity to be solely focused in delivering modules, research and etc. Doing peer reviews and etc may be impossible for some wikiversities (mine homewiki is one of them at that moment). For where it is incubating, I will think maybe at enwikiversity at this moment. --[[User:Cohaf|Cohaf]] ([[User talk:Cohaf|talk]]) 17:54, 3 June 2019 (UTC)
#{{support}} Need I say more? [[User:TheAwesomeHwyh|TheAwesomeHwyh]] ([[User talk:TheAwesomeHwyh|talk]]) 19:55, 3 June 2019 (UTC)
#{{support}} Yes, they will run into a lot of technical problems, but why not try? ;D — ''[[User:Jeblad|Jeblad]]'' 20:16, 3 June 2019 (UTC)
#<s>{{question}} Will wiki contributors who are not scholars have an opportunity to contribute to the project? [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:29, 4 June 2019 (UTC)</s> I now understand better per [https://en.wikiversity.org/wiki/WikiJournal_User_Group/Editors WikiJournal/Editors]. I follow this with my vote below. [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:36, 4 June 2019 (UTC)
#{{support}} The project. [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:36, 4 June 2019 (UTC)
#{{support}}. Yes. This will contribute tremendously towards the open access movement. [[User:OhanaUnited|<b><font color="#0000FF">OhanaUnited</font></b>]][[User talk:OhanaUnited|<b><font color="green"><sup>Talk page</sup></font></b>]] 00:42, 4 June 2019 (UTC)
#{{s}}. Project makes sense. [[User:Hiàn|Hiàn]] ([[User talk:Hiàn#top|talk]]) 01:20, 4 June 2019 (UTC)
#{{comment}} ({{ping|Mikael Häggström}}) The name of the proposed sister should '''not''' use camel case; that is, it should be either "Wikijournal" or, perhaps, "Wikijournals" (following the pattern of "Wikibooks"). The existing sisters don't use [[w:camel case|camel case]]: Wikipedia, Wiktionary, Wikinews, Wikibooks, etc. --[[User:Pi zero|Pi zero]] ([[User talk:Pi zero|talk]]) 03:14, 4 June 2019 (UTC)
#{{support}} the scope of WikiJournal is clearly different to Wikipedia and will be a beneficial addition to the Wikimedia family as per above. [[User:DaGizza|DaGizza]] ([[User talk:DaGizza|talk]]) 03:35, 4 June 2019 (UTC)
#{{support}}. I approve of the Wikipedia project and participate in it to some extent (though much more at Wikivoyage and Wikimedia Commons). However, what Wikipedia expressly lacks is peer-reviewed articles by experts. A free journal site where people don't have to pay loads of money to read cutting-edge papers on medicine and various other topics is an exciting idea and would be a great addition to the Wikimedia family. [[User:Ikan Kekek|Ikan Kekek]] ([[User talk:Ikan Kekek|talk]]) 04:23, 4 June 2019 (UTC)
#{{support}} - Dr Katherine Firth, La Trobe University [[Special:Contributions/121.211.87.1|121.211.87.1]] 05:50, 4 June 2019 (UTC) 
#{{Strong support}} — Improving the world's access to science may be considered one of the most important contributions the Wikimedia Foundation could ever achieve. With that being said, Tom Reller, Vice President of Global Communications at [[en:Elsevier|Elsevier]] recently said: ''"[[en:Elsevier#Plan S|If you think that information should be free of charge, go to Wikipedia]]"''. Perhaps we should prove him right. — [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 06:48, 4 June 2019 (UTC)

#{{support}} - [[user:lirazelf]] [[User:Lirazelf|Lirazelf]] ([[User talk:Lirazelf|talk]]) 07:23, 4 June 2019 (UTC)

Proposal: WikiJournal as a sister project

2019-06-04T07:55:11Z

Bryandamon: Minor spelling correction (review)

{{WikiJ top menu}}

{{DISPLAYTITLE:<span style="font-family:Century Gothic, Helvetica, sans serif">{{FULLPAGENAME}}</span>}}
{{New sister project proposal
| status = discussion
| project_name = WikiJournal
| tagline = Open-access peer-reviewed academic journals with no publication costs.
| project_description = A site where authors can write their works directly online. The works then undergo independent scholarly peer review before being officially published in the journal.

Currently hosted in Wikiversity: '''[[WikiJournal User Group]]''', with the three journals ''[[v:WikiJournal of Medicine|WikiJournal of Medicine]]'', ''[[v:WikiJournal of Science|WikiJournal of Science]]'', and ''[[v:WikiJournal of Humanities|WikiJournal of Humanities]]''.

It is a way of bridging the Wikipedia–academia gap by enabling academics, scholars and professionals to contribute expert knowledge to the Wikimedia movement in the familiar academic publishing format that directly rewards scholars with citable publications. Initial [[wikiversity:WikiJournal_User_Group/Publishing|publishing formats]] include: Reviews (many integrated into Wikipedia), Original research, Case studies, Images/galleries.

''See also:'' [[v:WikiJournal_User_Group|General landing page]] {{!}} [[v:WikiJournal of Medicine/About|About Wiki.J.Med.]] {{!}} [[v:WikiJournal of Science/About|About Wiki.J.Sci.]] {{!}} [[v:WikiJournal of Humanities/About|About Wiki.J.Hum.]]
| multilingual_wiki = Many language versions
| multilingual = Initially English, eventually many
| technical_reqs = A number of unique features will be useful:
* It should be possible to categorize users as authors, editors, and/or peer reviewers.
* Separate namespaces for articles yet to be peer-reviewed, equivalent to Wikipedia's [[en:Wikipedia:Drafts|Draftspace]], e.g. Draft: or Preprint: or equivalent. (Currently stored in [[:v:Category:Pre-prints_not_yet_included_in_WikiJournal_of_Medicine|category]] and as [[v:WikiJournal_of_Science/Submissions|list]])
* Some way of automatically numbering figures with <nowiki>[[file:...]]</nowiki> formatting (currently done in the <nowiki>{{</nowiki>[[v:template:fig|fig]]<nowiki>}}</nowiki> template).
**VisualEditor-compatible insertion of cross-references to figures
* It is important to have the option not to make certain pages publicly accessible (i.e., viewable by only author and editors). This avoids violating press embargos for unpublished articles and allows re-submission to other journals if rejected by WikiJournal. (Currently, confidential works must be emailed to {{nospam|submissions|wikijmed.org}}).
* Preferably there should be an option to have restricted viewer access to some files, discussions, and user identities (e.g., anonymous peer-reviewers).
* Simple on-wiki forms for users with no wikimarkup experience, and automated editing post-wiki (currently handled with google docs)
** submission of [[wikiversity:WikiJournal_User_Group/Potential_upcoming_articles|articles ready for review]]
** submission of [[wikiversity:WikiJournal_User_Group/Peer_reviewers|peer reviewer comments]]
* Automated features based on wikidata and/or bots
** synchronisation of [[v:template:article info|article info template]] on main and talk pages
** of the [[v:WikiJournal_of_Science/Potential_upcoming_articles|tracking sheets]] when reviewer comments submited
** [[wikiversity:WikiJournal_User_Group/Editorial_guidelines#Inclusion_of_approved_articles|metadata-submission to crossref]] of accepted articles
** addition of accepted articles to the current volume&issue
** XML annotation of articles in the [[:en:Journal_Article_Tag_Suite|JATS format]]
** addition of published articles into Wikidata
** transclusion/import/export with Wikipedia
** formatting of accepted articles into a specific PDF format (currently done manually via copy-paste to a [https://drive.google.com/file/d/0B4LQzkvkbO9YbEM5dktUUktTVlk/view DOCX template], which is then saved as a PDF. Another option could be to use the WikiMedia infrastructure as a [[w:Educational_Content_Sink|content sink]] and generate on demand other formats like docx, odt, LaTeX from the wiki syntax (e.g. via [http://www.pandoc.org PanDoc] or [[mw:Reading/Web/PDF_Functionality|MediaWiki PDF-export funtion]]). Requires e.g. two-column layout, inject logos, header styles etc. Manual tweaking of automated starting produced pdf would be ideal. Synchronisation to the latest version of the article would be ideal.
* Ideally we would like converters ''to'' wiki from DOCX and LaTeX so that articles can be more easily [[v:WikiJournal Preprints|submitted]].
* Specific left menu items
* Specific title fonts

| url =
'''Current''': hosted within Wikiversity links from:
*[http://Www.wikijmed.org www.wikijmed.org]
*[http://www.wikijsci.org www.wikijsci.org]
*[http://www.wikijhum.org www.wikijhum.org]
'''Ideal''': wikijournal.org (currently used for a separate start-up project by [[User:Fokebox]])<br>
'''Alternatively''': wikijournals.org, journal.wiki.org or journal.wikimedia.org
| logo = [[File:WikiJournal logo (flat blue yellow).svg|200px]]
Proposed logo matches current WMF sister project styles uses [https://trello.com/c/IRqbu8p4/15-color-swatches 2014 WMF colour palette]
<br>[[File:WikiJournal logo.svg|80px]] [[file:WikiJournal of Medicine logo.svg|80px]] [[file:WikiJournal of Science logo.svg|80px]] [[file:WikiJournal of Humanities logo.svg|80px]] [[file:WikiJournal Preprints logo.svg|80px]]
<br>Current logos of user group and specific journals within the group
<br>[[file:WikiJournal logo (flat black).svg|80px]] [[file:WikiJournal of Medicine logo (flat black).svg|80px]] [[file:WikiJournal of Science logo (flat black).svg|80px]] [[file:WikiJournal of Humanities logo (flat black).svg|80px]] [[file:WikiJournal Preprints logo (flat black).svg|80px]]
<br>Flat black version for small icons (including specific journals)

| more_settings =
| development_wiki = Not yet any separate technical-development wiki (e.g. in Wikimedia Labs)
| participants = Participants (editors, authors and peer reviewers) as of 2019-05-15
*'''Authors''': 172 ([[v:Template:Author_count|counting template]])
*'''Editorial boards'''': 62 ([[v:Template:Editor_count|counting template]])
*'''Associate editors''': 15 ([[v:Template:Editor_count|counting template]])
*'''Peer reviewers''': 70
*'''Additional on-wiki participants''': approx 5-10
'''Total''': approx 300-350
<br>[[Wikiversity:WikiJournal_User_Group/Editors|Editorial boards and associate editors]]
<br>[[WikiJournal_User_Group#Members_of_the_administrative_board|WikiJournal Admin board]]

Estimate of editors active in any given month:
*≥5 edits per month on-wiki: 25
*≥5 email to mailing lists: 25
*Monthly conference call meeting: 10
Notes: 1) a lot of work currently has to be done off-wiki. 2) Almost all peer reviewers only ever contribute once. 3) Many authors also only contribute once when depositing an article and once when responding to respond reviewer comments.

Readership from DOI-clicks in line with typical academic journals (800 per article).
{{Graph:Chart
| type = line
| width = 400
| height = 150
| xAxisTitle = 2018
| yAxisTitle = DOI resolutions per month
| x = Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov
| y = 1283,1312,1528,1289,1554,1970,1878,2036,4154,7780,12270
}}
}}

==Scenario==

# Many Wikipedia articles lack information (especially on complex topics)
#*Although [[w:wp:GA|GA]] and [[w:wp:FA|FA]] involve editorial review of content, there is little formal review from outside experts
#*Lack of quality images
#Lack of contributions from academic community
#*Wikipedia is often viewed with suspicion by academics
#*Academic authors often seek more recognition than provided in the history tab
#*Writing in Wikipedia is sufficiently unfamiliar to be a deterrent
#*Original research cannot be published on Wikipedia

==Possible solution==
The Wikipedia community and the academic community can be converged and unified through a journal initiative under the Wikimedia banner. The journals needs to adhere to international guidelines and standard procedures, in addition to being open-access and editable by all. WikiJournal can provide a prototype based on which journals for various themes and subjects can be built on.

This involves two broad aspects: The background structure and the journal contents.

===Background structure===
Background structure comprises:
* Journal policies: This can be customized based on the journal theme and subject, but would be common overall.
* Templates: Specific templates need to be designed for each journal. These templates would probably not be relevant to any other wikiproject.
* Technical parameters:
** Unlike other wikiprojects, the journal project calls for specialized logins as authors, editors and/or peer reviewers.
** We need to consider the possibility of one individual having multiple capacities, and the specific capacity being specified for an edit.
** Custom PDF-rendering facility.
** Possible on-wiki storage of confidential information (e.g. anon peer-reviewer identities).

===Journal contents===
* Anyone would be able to make a submission. Specification of legal name and contact details might be required.
* The submitted preprint contents would undergo a public peer-review by external experts and considered critically by an elected aditorial board before accepted into a journal's mainspace, or rejected.
* After acceptance, the editing capacities for the article would be restricted.
* A permalink in the form of [[W:Digital Object Identifier|Digital Object Identifier]] or DOI would be awarded to each article after publication.
* A citation format for academic publications would be specified.

==Present situation==
Three journals are currently published by the [[v:WikiJournal User Group|WikiJournal Publishing Group]]:

* [[v:WikiJournal of Medicine|''WikiJournal of Medicine'']] (est. 2014) for medicine and biomedicine (ISSN 2002-4436)
* [[v:WikiJournal of Science|''WikiJournal of Science'']] (est. 2018) for science, technology, engineering and mathematics (ISSN: 2470-6345)
* [[v:WikiJournal of Humanities|''WikiJournal of Humanities'']] (est. 2018) for humanities, arts, and social sciences (ISSN: 2639-5347)

WikiJMed was the original WikiJournal, and was the template for the subsequently established journals with broader scope (further info at [[v:WikiJournal of Medicine/About|WikiJournal of Medicine/About]]). Based on this initiative, WikiJSci (previously "Second Journal of Science") was developed in 2018 and was soon followed by WikiJHum. A composite [[WikiJournal User Group]] was formed in 2016 to overlook the development of such journals.

==Proposal==
A wiki that is open for everyone to contribute, at the same time with the features of scholarly journals in that the published works undergo independent peer-review by subject experts before publication. The authors are clearly credited at the top of their articles, making it more attractive for researchers and scholars to contribute. Articles are indexed and citable. Works may include images and reviews that are supported by secondary sources. Wikipedia and other Wikimedia sister projects can subsequently use material from these publications.

===Why separate Wikiproject===

* An internal [[Wikiversity:WikiJournal/Future as separate Wikimedia project|discussion]] revealed a consensus for a move to a separate Wikiproject.
* It calls for custom structure that would probably not be required by other Wikiprojects.
** Certain types of users would need to specify their real names and contact details.
** Login types might need to be specified.
** Custom templates.
* Better visibility and awareness. The current journals have limited viewership possibly due to lack of awareness across Wikimedia users.
* Grant requirements would follow a definite prototype.
* The scope is unique. This uniqueness needs to be identified.
** A separate link as another sister project will enhance its visibility to Wikimedia users would therefore enhance participation and impact.
* The scope does not exactly merge with:
** Wikiversity: Although there is partial overlap in relation to ''open research'', the scope of WikiJournal goes beyond that. ''Academic publications'' are not necessarily same as ''open academia'', ''open educational resources'' or ''learning projects''.
** Wikibooks: ''Academic publications'' are not necessarily same as ''open-content textbooks''.
** Wikipedia: Although Wikipedia is most read information source, it is often not given the credibility it deserves. While a few journals have started taking Wikipedia seriously, it still cannot claim the academic recognition that WikiJournal could claim.
* Impact metrics may not be applicable to any other wikiproject and may call for additional support from Wikimedia labs.
* Translation to other language wikis would call for standard protocols, unlike any other sister project.
* It is essential for journals to be enlisted in various databases and to follow various international protocols. A single repository for all such journals will help in minimising the problems of separate listing in such databases or central bodies.
* Established academic journals may set up spaces within such a project to implement similar reviews.

==Alternative proposals==
{{cot|Former proposals with similar scope|align=left|bg=#DDDDEE|border=0px|indent=10px;width:80%}}
*[[Wiki Scholarly Journals]]
*[[Wikiversity:Wikiversity:Journal of the future|Wikiversity:Journal of the future]]
*[[Wikisource:Wikisource:WikiProject Academic Papers|Wikisource:WikiProject Academic Papers]]
*[[Wikiversity:Wiki Journal]]
*[[Wikiversity:Portal:Wiki Scholar]]
*[[wikiversity:User:OpenScientist/Open_grant_writing/Encyclopaedia_of_original_research|Wikiversity:Encyclopaedia of original research]]
*[[strategy:Proposal:Journal_(A_peer-review_journal_to_allow/encourage_academics_to_write_Wikipedia_articles)|WikiStrategy:Journal]]
*[[Wikipedia Scientific Journal]]
{{cob}}
{{cot|Articles that mention the format|align=left|bg=#DDDDEE|border=0px|indent=10px;width:80%}}
* {{cite journal|last1=Masukume|first1=G|last2=Kipersztok|first2=L|last3=Das|first3=D|last4=Shafee|first4=T|last5=Laurent|first5=M|last6=Heilman|first6=J|title=Medical journals and Wikipedia: a global health matter|journal=The Lancet Global Health|date=November 2016|volume=4|issue=11|pages=e791|doi=10.1016/S2214-109X(16)30254-6|url=https://www.thelancet.com/journals/langlo/article/PIIS2214-109X(16)30254-6/fulltext}}
* {{Cite journal|last=Shafee|first=T|last2=Mietchen|first2=D|last3=Su|first3=A|date=August 2017|title=Academics can help shape Wikipedia|url=http://science.sciencemag.org/content/357/6351/557.2|journal=Science|volume=357|issue=6351|pages=557–558|doi=10.1126/science.aao0462}}
* {{Cite journal|last=Shafee|first=T|last2=Masukume|first2=G|last3=Kipersztok|first3=L|last4=Das|first4=D|last5=Häggström|first5=M|last6=Heilman|first6=J|date= August 2017|title=Evolution of Wikipedia’s medical content: past, present and future|url=http://jech.bmj.com/content/early/2017/08/24/jech-2016-208601|journal=JECH|doi=10.1136/jech-2016-208601|pmid=28847845}}
* {{Cite journal|url=https://www.hlinc.org.au/content/open-access/item/wikipedia-integrated-publishing-a-comparison-of-successful-models|title=Health Libraries - Wikipedia-integrated publishing: a comparison of successful models|publisher=Health inform.|volume=26 |issue=2|doi=10.13140/RG.2.2.27470.77129}}
* {{Cite journal|year=2017|title=WikiJournal of Medicine, the first Wikipedia-integrated academic journal|url=https://en.wikiversity.org/wiki/WikiJournal_of_Medicine/WikiJournal_of_Medicine,_the_first_Wikipedia-integrated_academic_journal|journal=WikiJournal of Medicine|volume=4|pages=|doi=10.15347/wjm/2017.001|last=Shafee|first =T|last2=Das|first2=D|last3=Masukume|first3=G|last4= Häggström|first4=M}}
* {{Cite journal|last=WikiJSci Editorial board|date=2018-06-01|title=The aims and scope of WikiJournal of Science|url=https://en.wikiversity.org/wiki/WikiJournal_of_Science/The_aims_and_scope_of_WikiJournal_of_Science|journal=WikiJournal of Science|language=en|volume=1|issue=1|pages=1|doi=10.15347/wjs/2018.001}}
{{cob}}
=== WikiJournal as a publishing house ===
'''WikiJournal as a publishing house''' I am a little confused about how a WikiJournal project would work: would other users be allowed to come along and edit already published research? Would it be like [http://www.scholarpedia.org/article/Main_Page Scholarpedia] where you need credentials? Rather than make a separate ''project'' as such, maybe "WikiJournal" could be a regularly-published periodical or a publishing imprint that has stable versions of articles that have been collaborated on at Wikiversity. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 18:13, 28 August 2016 (UTC)
:As summarized at [[Wikiversity:WikiJournal_of_Medicine/About#Structure|the structure of WikiJournal of Medicine]], anyone may edit pages, even published ones, but substantial edits to the main text of such articles would be reverted. Instead, users should then make a separate draft, and have that draft peer reviewed as well. Peer reviewers must be experts in the subject, but authors do not necessarily have to be. Collaborations at any site with a permitting license may be submitted. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 19:16, 2 September 2016 (UTC)

=== WikiJournal Public-Private-Versioning and Dynamic Paper Management in a Wiki ===
For a Journal the concept of '''[[Wikiversity:Public-Private-Versioning|Public-Private-Versioning]]''' could be used to facilitate a community based paper development (the community could contribute during the evolution of the paper - transparent history of the evolution of the paper, and private versions are created by a reviewing process (see [http://at6fui.weebly.com/open-community-approach.html Open Community Approach]).

Furthermore a KnitR-Backend or SageMath-Backend for Wikiversity papers can be used for statistical and/or numerical analysis of data for the paper (see '''[https://en.wikiversity.org/wiki/KnitR#Workflow_for_KnitR-Backend_for_in_Wikiversity.2FWikipedia KnitR in Wikiversity]''').
--[[User:Bert Niehaus|Bert Niehaus]] ([[User talk:Bert Niehaus|talk]]) 15:11, 11 August 2017 (UTC)
:Apologies for the delayed reply! I think the project would need some feedback on the best overall architecture to use behind the scenes (what can be done directly with mediawiki, and what can be third-party) so long as they interface well. One limitation we've had, for example, is that reviewers have to submit comments via a google form because there is not yet visualeditor in talkpages, and anonymous editors need to privately register their identity and affiliation with the editorial board. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 06:19, 1 June 2019 (UTC)

== Discussion ==

#{{Support}}. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 18:18, 21 August 2016 (UTC) Editor-in-chief, WikiJournal of Medicine
#'''Disagree with split''' I don't see why it's valuable to split this from WV--this is perfectly within its scope. In fact, it is one of the real triumphs of that project and splitting it off would probably be to the detriment of that site. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 21:52, 21 August 2016 (UTC)
#: Having Wikiversity lose WikiJournal might be a huge loss to you, [[User:Koavf|Justin]]. However, all's not lost for Wikiversity, and there is still hope for Wikiversity. Indeed, Wikiversity has English courses, like [[v:English as a second language]], most of which needs further improvements. Recently, I had to help one of users who utilized his <u>poor</u> English writing skills at English Wikipedia. To help him improve his English skills, I had to direct him to [[v:English]] and [[b:English]]. I received thanks for helping him. Therefore, Wikiversity may be needed for users who want to improve their English writing skills for English Wikipedia. Don't you think so? --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 05:44, 26 June 2017 (UTC); edited, 05:54, 26 June 2017 (UTC)
#::{{Ping|George Ho}} Honestly, it seems like your English is better in the months that I've seen you posting across WMF sites. I definitely believe that there is potential in Wikiversity but I just don't think this should split from it. We'll see how it goes. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 05:50, 26 June 2017 (UTC)
#::: Thanks for complimenting my English. ;) --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 05:54, 26 June 2017 (UTC)
#{{Support}} A journal needs specific tools. Having it as its own sister site would be ideal. [[User:Doc James|<span style="color:#0000f1">'''Doc James'''</span>]] ([[User talk:Doc James|talk]] · [[Special:Contributions/Doc James|contribs]] · [[Special:EmailUser/Doc James|email]]) 15:00, 22 August 2016 (UTC)
#::I continue to '''strongly support''' this project. This is an effective method of bringing in knowledge to our movement. This may also have potential for oral knowledge from indigenous peoples with a less robust publishing tradition.[[User:Doc James|<span style="color:#0000f1">'''Doc James'''</span>]] ([[User talk:Doc James|talk]] · [[Special:Contributions/Doc James|contribs]] · [[Special:EmailUser/Doc James|email]]) 11:24, 3 June 2019 (UTC)
#{{Support}} Very promising proposal --[[User:Athikhun.suw|Athikhun.suw]] ([[User talk:Athikhun.suw|talk]]) 00:52, 28 August 2016 (UTC)
#{{Support}} I agree with the split. I don't think it belongs with Wikiversity at all, which is for courses and curricula. It makes more sense to me, if anything, that it should be part of Wikibooks, as that is a place for publication of original scientific works. The process for a journal paper is different than a book however so I agree it should be separate. As for the project in general, I think the wiki approach to writing a scientific paper is potentially really great. I know PLOS has their own internal wiki for writing [http://collections.plos.org/topic-pages Topic Pages], which are review papers that are written and then eventually transferred to Wikipedia. Non-review papers, however, don't really make sense as part of Wikipedia, so it makes sense to develop them on their own wiki. [[User:Mvolz|Mvolz]] ([[User talk:Mvolz|talk]]) 17:44, 30 August 2016 (UTC)
#{{Support}} (finally after changing my mind three times: I never oppose a reasonable request if it has the support of the community --[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 23:06, 3 June 2019 (UTC))<s> '''Disagree with split''' (''Changed vote to '''neutral''' with the understanding that the real question is whether the wiki hosts confidential or "private" conversations'') <small>Original text:</small> Keep in mind that I speaking from the biased perspective of a [[v:Wikiversity:Custodianship|Wikiversity Custodian]] who is only marginally involved with this WikiJournal project. One reason Wikiversity would want to host the journals is that the software developed for WikiJournal could be useful on Wikiversity. An example of such software might include confidential communications between editors and referees that are held on-wiki (instead of on a remote user group). I have no idea whether Wikimedia is willing or even able to host such confidentiality, but it would also allow students and authors to collaborate privately. Also, Wikiversity would be interested in hosting student-run journals. I concede that the prospect of amateaurish student-journals might not be appealing to board members, and fully understand why the board might wish to separate from Wikiversity. If the board chooses to split, I will support that decision.</s> --[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 01:35, 3 September 2016 (UTC)
#:Confidential talks are currently held on a [https://groups.google.com Google Group], which can be used for students and authors even if WikiJournal is split from Wikiversity. Likewise, students have at least the same ability to start journals after a split. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 12:57, 3 September 2016 (UTC)
#::Allowing for confidential conversations on a Wikimedia sister-wiki would be a major departure from protocol. The wiki that does it will need an independent governing body for each journal or organization that uses it. Someday, it would be nice for universities, laboratories, and journals to have such capabilities. I am neutral about the current proposed split if the confidentality is not included: Without the confidentiality option, I see neither a reason for the split, nor any harm done by splitting away from Wikiversity. But if this new wiki is created with confidentiality options, it will likely recruit university and laboratory-based journals that wish to utilize this option. The question of whether to allow this confidentiality option is likely to go to the top levels of the Wikimedia corporation...Perhaps what we really need is for Google groups to host discussions in wikitext.--[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 19:03, 3 September 2016 (UTC)
#::{{ping|Mikael Häggström}} The private option is already availablae at '''https://wikiversity.miraheze.org/wiki/Main_Page'''--[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 16:46, 4 September 2016 (UTC)
#{{Support}} The scope is unique and can extend to a number of domains. Specific tools needed. Access rights need to be different. It is also important to have the option of certain pages not being publicly accessible such that press embargo for unpublished articles do not get violated and yet editors or peer reviewers get to work in wiki format. <font face="Segoe script">[[User:Diptanshu Das|'''<font color="#ff0000">D</font><font color="#ff6600">ip</font><font color="#009900">ta</font><font color="#0000ff">ns</font><font color="#6600cc">hu</font>''']][[User talk:Diptanshu Das|<sup>Talk</sup>]]</font> 12:21, 5 September 2016 (UTC)
#{{Support}} I definitely agree with this. If it does air how would the three statutes you mentioned be done? Would peer reviewer, editor, and author have different edit rights or be purely decorative, and would you have to apply for them? [[User:Iazyges|Iazyges]] ([[User talk:Iazyges|talk]]) 04:55, 6 September 2016 (UTC)
#:Good questions, [[User:Iazyges|Iazyges]]. I see no reason for editors to need any particular edit rights, and readers without any account should be able to edit too, [[Wikiversity:WikiJournal_of_Medicine/Editors#Editing_published_works|even published works under certain conditions]]. I think the author role is also rather decorative, since it's the quality of their works that matter. I think the peer reviewers should need to apply, so that we know they fulfill [[Wikiversity:WikiJournal_of_Medicine/Peer_reviewers#Criteria|the criteria]]. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 18:55, 15 September 2016 (UTC)
#{{Support}} per DocJames--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 11:59, 6 September 2016 (UTC)
#{{Support}} Because an open access journal is very different from WV and WB. --[[User:Netha Hussain|Netha Hussain]] ([[User talk:Netha Hussain|talk]]) 09:03, 13 September 2016 (UTC)
#{{Support}} because I'm looking for a project like this to publish some ideas. --[[User:Sophivorus|Felipe]] ([[User talk:Sophivorus|talk]]) 16:29, 20 November 2016 (UTC)
#{{Support}} - If this happens, I can read well the promising journal articles by academics. Though I can't write well the stuff, I can be a good reader to this. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 22:20, 18 January 2017 (UTC)
#:{{comment|Belated post-vote comment}}: I recently read peer reviews on scholarly articles and was amazed by comments and responses. I am also intrigued by the peer review templates, like [[v:en:Template:editor's comments]] and [[v:en:Template:Response]]. I [https://en.wikiversity.org/w/index.php?title=Talk:Radiocarbon_dating&diff=prev&oldid=1787502 fixed] a usage error recently, so I wonder whether the project can adopt either the templates or some software similar to MediaWiki's Support Desk or something like Wikinews's Comments (like [[:n:en:Comments:Judge jails 'monstrous' London serial killer Stephen Port|this example]]). Honestly, I found the templates less convenient for peer reviews, so I figured that some discussion software would be a better improvement. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 09:34, 5 December 2017 (UTC)
#{{Support}} -[[User:Richard923888|Richard923888]] ([[User talk:Richard923888|talk]]) 15:39, 21 January 2017 (UTC)
#{{Support}} - there is no reason why a separate journal cannot continue to link with WV but there is immense potential that cannot be achieved by remaining a sub-project. <span style="color:#29AB87">[[User:Green Giant|Green Giant]]</span> ([[User talk:Green Giant|talk]]) 15:09, 15 April 2017 (UTC)
#{{Support}} - This proposal has evolved and improved significantly since first proposed in 2016. The flagship ''WikiJournal of Medicine'' exemplifies what the project can achieve (see [http://dx.doi.org/10.15347%2Fwjm%2F2017.001 2017 editorial]). Starting up within Wikiversity was useful to incubate the project and prove that such a novel format is even feasible. Becoming a sister project would further support the initiative by adding legitimacy, support, and extra control of sidebar contents etc. There would remain a strong focus on generation, improvement, peer-review and re-integration of high-quality content into other WMF projects (especially Wikipedia), and a WikiJournal sister project would maintain strong ties to the other projects. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 01:03, 18 April 2017 (UTC)
#:I should note for transparency that since my original support vote, I'm now Editor-in-Chief of WikiJournal of Science, and I chair the administration board. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 00:07, 4 June 2019 (UTC)
#{{Support}} Great proposal!--[[User:Kiril Simeonovski|Kiril Simeonovski]] ([[User talk:Kiril Simeonovski|talk]]) 06:52, 9 May 2017 (UTC)
#{{Support}} For reasons adequately described above. · · · [[User:Pbsouthwood|Peter (Southwood)]] [[User talk:Pbsouthwood|<sup>(talk)</sup>]]: 08:09, 9 May 2017 (UTC)
#{{Support}} Great proposal with value for the academic community. <b>~<i><font color="#07517C">[[User:SuperHamster|Super]]</font></i><font color="#6FA23B">[[User:SuperHamster|Hamster]]</font></b> <small>[[User talk:SuperHamster|Talk]] [[Special:Contributions/SuperHamster|Contribs]]</small> 17:00, 9 May 2017 (UTC)
#{{Support}} more than that it is exactly what i had in mind because the lack of open source credited material is recurrent fact on wikipedia and it will expand wikimedia scope. --[[Special:Contributions/167.63.49.24|167.63.49.24]] 02:52, 2 June 2017 (UTC)
#{{Support}} - Seems like a reasonable proposal, I don't see why it shouldn't at least be given a try. I think the challenge will mostly consist of getting experts in various fields to peer-review, but that's not impossible to do. [[User:InsaneHacker|InsaneHacker]] ([[User talk:InsaneHacker|talk]]) 06:27, 2 July 2017 (UTC)
#<s>{{oppose}} they don't need an entire sister project. It has to stay in [[v:|WV]].</s>this user voted 2x, therefore have struck one vote--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 15:29, 24 October 2017 (UTC)
#:{{strong oppose}} to separate login. Just add the obligation to fill an ''informations'' tab in ''Preferences'' to allow contributing [[User:CreativeC38|CreativeC38]] ([[User talk:CreativeC38|talk]]) 10:19, 6 July 2017 (UTC)
#::{{Ping|CreativeC38}} Why does it ''have'' to stay on WV? You don't think there's any merit whatsoever to having it as a separate site instead of a subpage on WV in terms of presentation, attracting experts etc.? [[User:InsaneHacker|InsaneHacker]] ([[User talk:InsaneHacker|talk]]) 00:24, 8 July 2017 (UTC)
#:: Also, the "oppose" and "strong oppose" vote [https://meta.wikimedia.org/w/index.php?title=WikiJournal&diff=16967843&oldid=16955738 are yours]. I'm informing readers to avoid misleads. BTW, sometimes you feel that Wikiversity won't be the same without WikiJournal. However, Wikiversity has been Wikiversity, especially without WikiJournal. Also, it has some good lessons for others to read, like [[v:English]]. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 03:48, 8 July 2017 (UTC)
#{{Support}} - I think it is to Wikiversity's detriment that WikiJournal find a separate home, however, it does seem to be a better approach for WikiJournal itself, and it should attract more users to the wiki community. I trust that WikiJournal will encourage academics to develop lessons and courses supporting their work at Wikiversity. -- [[User:Dave Braunschweig|Dave Braunschweig]] ([[User talk:Dave Braunschweig|talk]]) 21:49, 8 July 2017 (UTC)
#{{Support}} I think WikiJournal would have better chances to develop and to engage with expert communities if it were a sister project. --<font style="font-family:Monotype Corsiva; font-size:15px;"> [[User:Daniel Mietchen|Daniel Mietchen]] ([[User talk:Daniel Mietchen|talk]]) </font> 17:38, 31 August 2017 (UTC)
#{{Support}} I agree my previous speaker. Good point -- <span style="font-variant:small-caps">[[User:DerFussi|Der]][[User talk:DerFussi|Fussi]]</span> 06:12, 13 September 2017 (UTC)
#{{s}} Per others. -- [[User:Thennicke|Thennicke]] ([[User talk:Thennicke|talk]]) 23:23, 16 October 2017 (UTC)
#'''Comment''' I propose to lessen the requirement to first make the article available in wiki format. Consider my case: I wrote a book (i.e. a very long article) in PDF format (generated from LaTeX) with my original research in mathematics and make it publicly available under an open license. I have a trouble publishing it, because journals don't publish 380 pages articles and book publishers refuse to publish a book which is already available online. I want to allow me to submit the PDF file and be reviewed in WikiJournal project. Note that converting PDF into wiki markup would be a hard work, and this way it would be needed to update after each change in my book (e.g. when I add a solution of a conjecture or correct a typo). --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 23:44, 26 October 2017 (UTC)
#:{{re|VictorPorton}} We definitely hope to implement some easier ways of importing LaTeX, DOCX and PDF submissions on the [[v:WikiJournal Preprints|submissions page]]. That will likely require help from the WMF's dev team. Currently, the main conversion option is probably [http://pandoc.org Pandoc]. We have had people submit as docx files, and the journal editors have manually reformatted for wikimarkup, but that's not a scalable solution. Note that currently only Wiki.J.Med. is accepting original research, whist the other journals starting up are focusing on review articles (at least initially) since these are 'safer' options for building the journals early on. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 02:55, 27 October 2017 (UTC)
#::It seems that we will never (or at least in near 50 years) have a good automated conversion from LaTeX to wiki. I propose not to convert but to allow the author to upload a PDF file and publish in the wiki just a link to author's files, not the article itself in wiki markup. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 12:33, 27 October 2017 (UTC)
#::We also need some reasonable policy about updates of already published articles. For example arXiv allows to upload more than one version of an article. (This is especially important with articles building a theory rather than proving a single result.) We need it too. Probably every change should be peer reviewed. Or we can trust authors that they improve their materials over time not make it worse. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 12:39, 27 October 2017 (UTC)
#:::The downside of if we were to have only a pdf version and no wikimarkup version, is that it would make it hard to integrate material into other Wikimedia projects (one of the current main goals of the journals). However, this is not set in stone, so could change. As for multiple versions - I agree with the need for more specific guidelines (it happens not to have come up yet). In addition to the history tab record of all edits during drafting on the preprint server, my expectation is that anything that changes content of a published article would have to be re-reviewed to retain legitimacy. Indeed I can imagine that people could publish updated 'versions' of a review article, as already happens for textbooks. I'd suggest more in-depth discussion be on the main [[v:Talk:WikiJournal_User_Group|WikiJournal discussion page]]. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 13:51, 27 October 2017 (UTC)
#::::Anyway my book won't be completely copied to Wikipedia. So to convert the entire book and every its part into wiki markup format is just largely useless work. If we need to publish some part in a wiki, we can convert parts of the book or article on as-needed basis. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 22:03, 27 October 2017 (UTC)
#::::: Hello, [[User:VictorPorton|Victor]]. Here is [[v:en:WikiJournal Preprints]], which has instructions on sending PDF files via email and provides email address for those wanting to send PDF files. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 02:15, 29 October 2017 (UTC)
#{{Support}} This sounds like "a hidden gem 💎" situation where something good is hidden in something else, people who would be interested in this but otherwise not in the Wikiversity might be able to see this sooner if it weren't "hidden away". --[[User:Donald Trung|Donald Trung]] ([[User talk:Donald Trung|Talk 🤳🏻]]) ([[Steward requests/Global/2017-08#Global lock Donald Trung and sockpuppets|My global lock 😒🌏🔒]]) ([[Steward requests/Global/2017-09|My global unlock 😄🌏🔓]]) 11:44, 10 November 2017 (UTC)
#{{support}} Very important project. [[User:Ammarpad|Ammarpad]] ([[User talk:Ammarpad|talk]]) 14:45, 18 November 2017 (UTC)
#{{Support}} This proposal has a unique scope, and would have been the only WMF project to seem trustworthy for referencing by most of academics. In addition to the potential features listed on the top, this project would require much stricter internal procedures and hence Wikiversity does not fit in its current form. --[[User:Strange quark|Strange quark]] ([[User talk:Strange quark|talk]]) 13:30, 30 December 2017 (UTC)
#'''Support''' I'm ready to give a hand for french version of this sister project. [[User:Lionel Scheepmans|Lionel Scheepmans]] <sup><big>✉ </big> [[User talk:Lionel Scheepmans|Contact]]</sup> <sub>French native speaker, sorry for my [[w:dysorthography|dysorthography]]</sub> 20:28, 25 February 2018 (UTC)
#{{support}} [[User:NMaia|NMaia]] ([[User talk:NMaia|talk]]) 09:32, 26 March 2018 (UTC)
#'''question'''('''comment''') we have 26 signatures above plus journals which have been added[https://en.wikiversity.org/wiki/WikiJournal_of_Science] and [https://en.wikiversity.org/wiki/WikiJournal_of_Humanities] ...so where are we in terms of the process of this proposal?(how much longer)thank you--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 20:27, 11 September 2018 (UTC)
#*{{Re|Ozzie10aaaa}} yes, previously comment has been from people who happened to come across the page. The [[Sister Projects Committee#Current%20new%20project%20process|Sister Projects Committee]] suggested the gathering of contributor data and to make sure that people in different projects are aware of the proposal, so I have placed some notifications around a few areas in wikipedia, wikidata and mailing lists. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 09:31, 2 June 2019 (UTC)
#{{support}} [[User:Reboot01|Reboot01]] ([[User talk:Reboot01|talk]]) 13:47, April 25, 2019 (UTC)
#{{support}} Splitting it could really allow greater participation in WJ from outside stakeholders. [[User:StudiesWorld|StudiesWorld]] ([[User talk:StudiesWorld|talk]]) 10:20, 16 May 2019 (UTC)
#{{support}} interesting proposal and splitting can make the arrangements much better! '''--'''[[User:علاء |<font size="3" face="Script MT Bold" style="color:black;">Alaa</font> ]] [[User_talk:علاء |:)..!]] 04:29, 2 June 2019 (UTC)
#{{support}} as article author - (Michael Stear) [[Special:Contributions/131.172.248.203|131.172.248.203]] 04:30, 2 June 2019 (UTC) 
#{{support}} as article author - (Kholhring Lalchhandama) [[User:Chhandama|Chhandama]] ([[User talk:Chhandama|talk]]) 06:20, 2 June 2019 (UTC) 
#{{support}} - (Fiona Mackinnon) [[Special:Contributions/49.180.152.237|49.180.152.237]] 04:57, 2 June 2019 (UTC) 
#{{support}} - [[User:Learnerktm|Learnerktm]] ([[User talk:Learnerktm|talk]]) 06:23, 2 June 2019 (UTC) 
#{{support}} as article author - (Andrew Z. Colvin) [[User:Azcolvin429|Azcolvin429]] ([[User talk:Azcolvin429|talk]]) 06:35, 2 June 2019 (UTC) 
#{{support}} as article author - [[v:User:Tsirel|Boris Tsirelson]]. WikiJournal evidently is very different from (the rest of) Wikiversity. [[User:Tsirel|Tsirel]] ([[User talk:Tsirel|talk]]) 07:00, 2 June 2019 (UTC)
#{{support}} - as article author - other WV articles I've read have little to do with those of WJ. However, I can understand the concerns raised here[https://en.wikipedia.org/wiki/Wikipedia_talk:Featured_article_candidates#A_proposal_for_WikiJournals_to_become_a_new_sister_project]. [[User:Funk Monk|FunkMonk]] ([[User talk:FunkMonk|talk]]) 07:00, 2 June 2019 (UTC) 
#{{support}} as article author - (Abdulmutalab Musa) [[User:Laamiido|Laamiido]] ([[User talk:Laamiido|talk]]) 07:39, 2 June 2019 (UTC) 
# {{support}} as article reviewer - (Gregor Stiglic) [[Special:Contributions/100.8.28.171|100.8.28.171]] 10:18, 2 June 2019 (UTC) 
#{{support}} as article author - (Lauren Gawne) [[Special:Contributions/14.203.84.11|14.203.84.11]] 10:38, 2 June 2019 (UTC) 
#{{support}} as article author -(Ozzie Anis)--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 10:57, 2 June 2019 (UTC)
#{{support}} as article author - [[User:Andrew Dalby|Andrew Dalby]] ([[User talk:Andrew Dalby|talk]]) 11:15, 2 June 2019 (UTC)
#{{support}} as article author - I vote FOR WikiJournal to become a full 'Sister Project' of Wikipedia. (Deepesh Nagarajan) [[Special:Contributions/14.139.128.17|14.139.128.17]] 11:46, 2 June 2019 (UTC)
#{{support}} [[User:Dank|Dank]] ([[User talk:Dank|talk]]) 12:23, 2 June 2019 (UTC)
#{{s}} [[User:Richard Nevell|Richard Nevell]] ([[User talk:Richard Nevell|talk]]) 12:49, 2 June 2019 (UTC)
#{{support}} - [[User:FULBERT|FULBERT]] ([[User talk:FULBERT|talk]]) 13:02, 2 June 2019 (UTC) - For journals to be taken seriously as academic and peer-reviewed contributors to knowledge, they need to appear solid and independent. Wikiversity is a wonderful idea, though it is not as useful as a dedicated space for open, peer-reviewed journal work. I believe that having a dedicated project space may also allow for some dedicated resources and visibility. This is consistent with the Wikimedia strategy to become the essential infrastructure of the ecosystem of free knowledge through knowledge as a service and knowledge equity.
#{{support}} as article reviewer - Niclas Borinder [[Special:Contributions/81.227.107.149|81.227.107.149]] 13:37, 2 June 2019 (UTC)
#{{support}} We have some details to sort but yes, for the spirit of it all and for committing significant resources to advance this idea in the immediate future, I support. [[User:Bluerasberry|<span style="background:#cedff2;color:#11e">''' Blue Rasberry '''</span>]][[User talk:Bluerasberry|<span style="background:#cedff2;color:#11e">(talk)</span>]] 14:10, 2 June 2019 (UTC)
#{{support}} as article author - Dudley Miles. I have found the project valuable in getting reviews by academic experts to raise the standard of an article. [[User:Dudley Miles|Dudley Miles]] ([[User talk:Dudley Miles|talk]]) 14:18, 2 June 2019 (UTC)
#{{support}} - [[User:Jacknunn|Jacknunn]] ([[User talk:Jacknunn|talk]]) 14:30, 2 June 2019 (UTC) This project has huge potential to bring peer-review to Wikipedia and have clear integration into the most famous Wikimedia project. Wikiversity has huge potential - but to speak frankly, it is not a University- The Open University is, and was very ahead of its time and one day, Wikimedia might partner or create something similar under this name. For now, it is not a University, and so is confusing to people not intimately familiar with Wikimedia projects (99.9999% of humanity). Even if it were a proper University, most universities create separate affiliated publishing houses (https://en.wikipedia.org/wiki/List_of_university_presses). I think simplifying this project as much as possible - that is 'creating peer-reviewed Wikimedia content using the familiar publishing norms of established peer-reviewed journals' is a good start, one that Wikimedia can build on and improve in alignment with the founding principles of the foundation. Project S is coming, let's be ready to meet it with a great front end and and even better back one! :)
#{{support}} Thank you for this well thought-out proposal, which addresses many limitations that have been identified over the course of the last few years. There are great benefits in separate sister project status, and honestly I don't think WV is a very suitable place for the journals to remain at at this point. --[[User:Elmidae|Elmidae]] ([[User talk:Elmidae|talk]]) 14:40, 2 June 2019 (UTC)
#{{oppose}} Various "technical requirements" violate the [[Founding principles]], especially the second one. While I understand the reasons, I don't think that such a project should be part of the Wikimedia "wiki family"; academic publishing works primarily through the reputation of its authors and publishers while Wikimedia projects work mostly on the basis of the dedicated interest of number of editors (both casual, sporadic, one time and regular ones) irrespective of their qualifications and trying to put both of them together isn't going to work due to the culture contrast. [[User:Jo-Jo Eumerus|Jo-Jo Eumerus]] ([[User talk:Jo-Jo Eumerus|talk]], [[Special:CentralAuth/Jo-Jo Eumerus|contributions]]) 15:18, 2 June 2019 (UTC)
#*that 'culture contrast' has existed for many years, a journal of this nature would only be a positive...IMO--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 16:12, 2 June 2019 (UTC)
#*:Yeah, and we've had problems with it. I don't disagree with the existence of such a project, I object to making it part of the Wikimedia family. [[User:Jo-Jo Eumerus|Jo-Jo Eumerus]] ([[User talk:Jo-Jo Eumerus|talk]], [[Special:CentralAuth/Jo-Jo Eumerus|contributions]]) 16:25, 2 June 2019 (UTC)
#{{oppose}}, per Jo-Jo Eumerus. - [[User:SchroCat|SchroCat]] ([[User talk:SchroCat|talk]]) 16:00, 2 June 2019 (UTC)
#{{support}} as article reviewer - Jennifer Dawson [[User:JenOttawa|JenOttawa]] ([[User talk:JenOttawa|talk]]) 16:05, 2 June 2019 (UTC) 
#{{support}} as a Wikijournal contributor. One of the reasons I support this is that a journal would let us go farther than writing for an encyclopedia. Often, Wikipedia policies such as [https://en.wikipedia.org/wiki/Wikipedia:No_original_research NOR (no original research)] hinders our ability to be academic. For example, the article I was honored to submit, [https://en.wikiversity.org/wiki/WikiJournal_of_Humanities/Themes_in_Maya_Angelou%27s_autobiographies Themes in Maya Angelou's autobiographies], isn't comprehensive because there are no sources to fill in some aspects of the topic. Although I'm not an academic expert, my experience as a WP editor of this article and others like it has made me into an expert about Dr. Angelou. I'd like to see the mission of the Wikijournal expand to allow original research, in order to expand the comprehensiveness of topics. In that way, we can improve upon the academic nature of WP and fill in the gaps imposed upon us by WP policies and procedures and the gaps that are out there in academic literature. [[User:Figureskatingfan|Figureskatingfan]] ([[User talk:Figureskatingfan|talk]]) 21:24, 2 June 2019 (UTC)
#::'''Comment''' Agree. The same problem with Wikipedia in the (quite far) topic - mathematics. Wikipedia's principle is "to inform, not teach/explain", but readers really need explanations and examples, which often leads to violations of the "no original research" norm, and frustration on both sides, readers and editors. WikiJournal is able to complement Wikipedia with explanations and examples using expertise. For example, my recent submission (explanatory essay) "[[v:WikiJournal Preprints/Can each number be specified by a finite text?]]". Wikiversity admits original research, but does not restrict it by peer refereeing, which is a completely different story. [[User:Tsirel|Tsirel]] ([[User talk:Tsirel|talk]]) 05:24, 3 June 2019 (UTC)
#{{support}} - (Tseenster) [[User:Tseenster|Tseenster]] ([[User talk:Tseenster|talk]]) 23:43, 2 June 2019 (UTC) 
# {{oppose}} primarily per Jo-Jo Eumerus, with the added caveat that according to [[mw:Template:Page security extension disclaimer]], {{tq|MediaWiki was not written to provide per-page access restrictions, and almost all hacks or patches promising to add them will likely have flaws somewhere}}, meaning that the technical requirements violate not only founding principles but also the very way the code for MediaWiki is designed. [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">has returned</sub>]] 00:39, 3 June 2019 (UTC)
#{{support}} - [[User:Benoit Rochon|Benoit Rochon]] ([[User talk:Benoit Rochon|talk]]) 01:36, 3 June 2019 (UTC)
#{{support}} - as one of the few new projects that I have seen that makes sense. This one just fits. [[User:Philippe|--Philippe]] ([[User talk:Philippe|talk]]) 01:59, 3 June 2019 (UTC)
#{{support}} - Wade Kelly [[User:Mrkellar|Mrkellar]] ([[User talk:Mrkellar|talk]]) 06:00, 3 June 2019 (UTC) 
#{{support}} - Steven Chang [[User:Gixibyte|Gixibyte]] ([[User talk:Gixibyte|talk]]) 06:40, 3 June 2019 (UTC)
#{{support}} - [[User:Rwatson1955|Rwatson1955]] ([[User talk:Rwatson1955|talk]]) 07:27, 3 June 2019 (UTC) 
#{{support}} as article author - (Ignacio López) [[User:Munguira|Munguira]] ([[User talk:Munguira|talk]]) 08:04, 3 June 2019 (UTC) 
#{{support}} [[User:Mardetanha|<font face="Rage Italic" size="4" style="color:#000000;color:black"><i>Mardetanha</i></font>]] <sup><span style="font-family:Italic;color:black">[[user_talk:Mardetanha|talk]]</span></sup> 09:08, 3 June 2019 (UTC)
#{{s}}.--[[User:Vulphere|<span style="background:#000000; color:white; padding:2px;">Vulp</span>]][[User talk:Vulphere|<span style="background:#00b700; color:white; padding:2px;">here</span>]] 09:24, 3 June 2019 (UTC)
#{{support}} - (Niall O’Mara) [[User:Ngdomara|Ngdomara]] ([[User talk:Ngdomara|talk]]) 09:57, 3 June 2019 (UTC)  support
# {{support}} as article reviewer - Herbert Haller
# {{s}} - this project has a lot of potential and it makes sense to give it the resources it needs to grow. [[User:Sic19|Simon Cobb]] ([[User:Sic19|Sic19]] ; [[User_talk:Sic19|talk page]]) 13:34, 3 June 2019 (UTC)
#{{support}} - Amy Fountain [[User:AmyFou|AmyFou]] ([[User talk:AmyFou|talk]]) 14:31, 3 June 2019 (UTC) 
#{{support}} - Arfon Smith [[Special:Contributions/128.177.88.206|128.177.88.206]] 14:50, 3 June 2019 (UTC) 
#{{question}} – I assume any new journals are going to incubate within this project, right? (I don't see us being equipped at Incubator to get involved.) [[User:StevenJ81|StevenJ81]] ([[User talk:StevenJ81|talk]]) 17:08, 3 June 2019 (UTC)
#{{support}} - This is a solid proposal with a healthy ecosystem of participants. Full-discloure, my wife among them. :) Opposing this based upon technical requirements is a distraction. People use tools other than MediaWiki everyday to support the movement. If we could, I'd rather folks use an open-source solution than have their work buried in some closed-source system owned by for-profit company. Besides, [[Community_health_initiative/Partial_blocks|partial blocks exist in MediaWiki]] and extending that to other use cases is a strength of a flexible open-source platform. Not to get too into the weeds, but it's also commented as "preferred", not a do-or-die requirement for success. These are smart people and I'm sure they can get it done. :) So again, technical fiddly-bits are a weak argument to oppose and I'd rather see us make a strong argument to support a burgeoning new project. [[User:Ckoerner|Ckoerner]] ([[User talk:Ckoerner|talk]]) 17:51, 3 June 2019 (UTC)
#{{support}} Yes, I find it helpful that wikijournal is it's own project sort of like how wikiversity is it's own project and not included into wikibooks. Wikijournal is a complex process and the peer review process isn't easy for an open project to do, yes, enwikiversity did a great job but I guess with more specific structure, it will be more conducive for academics to review journals which then will allow more growth. For this structure, I will hope it can be developed with wikiversity in mind (in some sense like OTRS can be shared with all projects - the tool and etc). I find it more useful for wikiversity to be solely focused in delivering modules, research and etc. Doing peer reviews and etc may be impossible for some wikiversities (mine homewiki is one of them at that moment). For where it is incubating, I will think maybe at enwikiversity at this moment. --[[User:Cohaf|Cohaf]] ([[User talk:Cohaf|talk]]) 17:54, 3 June 2019 (UTC)
#{{support}} Need I say more? [[User:TheAwesomeHwyh|TheAwesomeHwyh]] ([[User talk:TheAwesomeHwyh|talk]]) 19:55, 3 June 2019 (UTC)
#{{support}} Yes, they will run into a lot of technical problems, but why not try? ;D — ''[[User:Jeblad|Jeblad]]'' 20:16, 3 June 2019 (UTC)
#<s>{{question}} Will wiki contributors who are not scholars have an opportunity to contribute to the project? [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:29, 4 June 2019 (UTC)</s> I now understand better per [https://en.wikiversity.org/wiki/WikiJournal_User_Group/Editors WikiJournal/Editors]. I follow this with my vote below. [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:36, 4 June 2019 (UTC)
#{{support}} The project. [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:36, 4 June 2019 (UTC)
#{{support}}. Yes. This will contribute tremendously towards the open access movement. [[User:OhanaUnited|<b><font color="#0000FF">OhanaUnited</font></b>]][[User talk:OhanaUnited|<b><font color="green"><sup>Talk page</sup></font></b>]] 00:42, 4 June 2019 (UTC)
#{{s}}. Project makes sense. [[User:Hiàn|Hiàn]] ([[User talk:Hiàn#top|talk]]) 01:20, 4 June 2019 (UTC)
#{{comment}} ({{ping|Mikael Häggström}}) The name of the proposed sister should '''not''' use camel case; that is, it should be either "Wikijournal" or, perhaps, "Wikijournals" (following the pattern of "Wikibooks"). The existing sisters don't use [[w:camel case|camel case]]: Wikipedia, Wiktionary, Wikinews, Wikibooks, etc. --[[User:Pi zero|Pi zero]] ([[User talk:Pi zero|talk]]) 03:14, 4 June 2019 (UTC)
#{{support}} the scope of WikiJournal is clearly different to Wikipedia and will be a beneficial addition to the Wikimedia family as per above. [[User:DaGizza|DaGizza]] ([[User talk:DaGizza|talk]]) 03:35, 4 June 2019 (UTC)
#{{support}}. I approve of the Wikipedia project and participate in it to some extent (though much more at Wikivoyage and Wikimedia Commons). However, what Wikipedia expressly lacks is peer-reviewed articles by experts. A free journal site where people don't have to pay loads of money to read cutting-edge papers on medicine and various other topics is an exciting idea and would be a great addition to the Wikimedia family. [[User:Ikan Kekek|Ikan Kekek]] ([[User talk:Ikan Kekek|talk]]) 04:23, 4 June 2019 (UTC)
#{{support}} - Dr Katherine Firth, La Trobe University [[Special:Contributions/121.211.87.1|121.211.87.1]] 05:50, 4 June 2019 (UTC) 
#{{Strong support}} — Improving the world's access to science may be considered one of the most important contributions the Wikimedia Foundation could ever achieve. With that being said, Tom Reller, Vice President of Global Communications at [[en:Elsevier|Elsevier]] recently said: ''"[[en:Elsevier#Plan S|If you think that information should be free of charge, go to Wikipedia]]"''. Perhaps we should prove him right. — [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 06:48, 4 June 2019 (UTC)

#{{support}} - [[user:lirazelf]] [[User:Lirazelf|Lirazelf]] ([[User talk:Lirazelf|talk]]) 07:23, 4 June 2019 (UTC)

Proposal: WikiJournal as a sister project

2019-06-04T06:48:40Z

Bryandamon: /* Discussion */ Added my support.

{{WikiJ top menu}}

{{DISPLAYTITLE:<span style="font-family:Century Gothic, Helvetica, sans serif">{{FULLPAGENAME}}</span>}}
{{New sister project proposal
| status = discussion
| project_name = WikiJournal
| tagline = Open-access peer-reviewed academic journals with no publication costs.
| project_description = A site where authors can write their works directly online. The works then undergo independent scholarly peer review before being officially published in the journal.

Currently hosted in Wikiversity: '''[[WikiJournal User Group]]''', with the three journals ''[[v:WikiJournal of Medicine|WikiJournal of Medicine]]'', ''[[v:WikiJournal of Science|WikiJournal of Science]]'', and ''[[v:WikiJournal of Humanities|WikiJournal of Humanities]]''.

It is a way of bridging the Wikipedia–academia gap by enabling academics, scholars and professionals to contribute expert knowledge to the Wikimedia movement in the familiar academic publishing format that directly rewards scholars with citable publications. Initial [[wikiversity:WikiJournal_User_Group/Publishing|publishing formats]] include: Reviews (many integrated into Wikipedia), Original research, Case studies, Images/galleries.

''See also:'' [[v:WikiJournal_User_Group|General landing page]] {{!}} [[v:WikiJournal of Medicine/About|About Wiki.J.Med.]] {{!}} [[v:WikiJournal of Science/About|About Wiki.J.Sci.]] {{!}} [[v:WikiJournal of Humanities/About|About Wiki.J.Hum.]]
| multilingual_wiki = Many language versions
| multilingual = Initially English, eventually many
| technical_reqs = A number of unique features will be useful:
* It should be possible to categorize users as authors, editors, and/or peer reviewers.
* Separate namespaces for articles yet to be peer-reviewed, equivalent to Wikipedia's [[en:Wikipedia:Drafts|Draftspace]], e.g. Draft: or Preprint: or equivalent. (Currently stored in [[:v:Category:Pre-prints_not_yet_included_in_WikiJournal_of_Medicine|category]] and as [[v:WikiJournal_of_Science/Submissions|list]])
* Some way of automatically numbering figures with <nowiki>[[file:...]]</nowiki> formatting (currently done in the <nowiki>{{</nowiki>[[v:template:fig|fig]]<nowiki>}}</nowiki> template).
**VisualEditor-compatible insertion of cross-references to figures
* It is important to have the option not to make certain pages publicly accessible (i.e., viewable by only author and editors). This avoids violating press embargos for unpublished articles and allows re-submission to other journals if rejected by WikiJournal. (Currently, confidential works must be emailed to {{nospam|submissions|wikijmed.org}}).
* Preferably there should be an option to have restricted viewer access to some files, discussions, and user identities (e.g., anonymous peer-reviewers).
* Simple on-wiki forms for users with no wikimarkup experience, and automated editing post-wiki (currently handled with google docs)
** submission of [[wikiversity:WikiJournal_User_Group/Potential_upcoming_articles|articles ready for reiew]]
** submission of [[wikiversity:WikiJournal_User_Group/Peer_reviewers|peer reviewer comments]]
* Automated features based on wikidata and/or bots
** synchronisation of [[v:template:article info|article info template]] on main and talk pages
** of the [[v:WikiJournal_of_Science/Potential_upcoming_articles|tracking sheets]] when reviewer comments submited
** [[wikiversity:WikiJournal_User_Group/Editorial_guidelines#Inclusion_of_approved_articles|metadata-submission to crossref]] of accepted articles
** addition of accepted articles to the current volume&issue
** XML annotation of articles in the [[:en:Journal_Article_Tag_Suite|JATS format]]
** addition of published articles into Wikidata
** transclusion/import/export with Wikipedia
** formatting of accepted articles into a specific PDF format (currently done manually via copy-paste to a [https://drive.google.com/file/d/0B4LQzkvkbO9YbEM5dktUUktTVlk/view DOCX template], which is then saved as a PDF. Another option could be to use the WikiMedia infrastructure as a [[w:Educational_Content_Sink|content sink]] and generate on demand other formats like docx, odt, LaTeX from the wiki syntax (e.g. via [http://www.pandoc.org PanDoc] or [[mw:Reading/Web/PDF_Functionality|MediaWiki PDF-export funtion]]). Requires e.g. two-column layout, inject logos, header styles etc. Manual tweaking of automated starting produced pdf would be ideal. Synchronisation to the latest version of the article would be ideal.
* Ideally we would like converters ''to'' wiki from DOCX and LaTeX so that articles can be more easily [[v:WikiJournal Preprints|submitted]].
* Specific left menu items
* Specific title fonts

| url =
'''Current''': hosted within Wikiversity links from:
*[http://Www.wikijmed.org www.wikijmed.org]
*[http://www.wikijsci.org www.wikijsci.org]
*[http://www.wikijhum.org www.wikijhum.org]
'''Ideal''': wikijournal.org (currently used for a separate start-up project by [[User:Fokebox]])<br>
'''Alternatively''': wikijournals.org, journal.wiki.org or journal.wikimedia.org
| logo = [[File:WikiJournal logo (flat blue yellow).svg|200px]]
Proposed logo matches current WMF sister project styles uses [https://trello.com/c/IRqbu8p4/15-color-swatches 2014 WMF colour palette]
<br>[[File:WikiJournal logo.svg|80px]] [[file:WikiJournal of Medicine logo.svg|80px]] [[file:WikiJournal of Science logo.svg|80px]] [[file:WikiJournal of Humanities logo.svg|80px]] [[file:WikiJournal Preprints logo.svg|80px]]
<br>Current logos of user group and specific journals within the group
<br>[[file:WikiJournal logo (flat black).svg|80px]] [[file:WikiJournal of Medicine logo (flat black).svg|80px]] [[file:WikiJournal of Science logo (flat black).svg|80px]] [[file:WikiJournal of Humanities logo (flat black).svg|80px]] [[file:WikiJournal Preprints logo (flat black).svg|80px]]
<br>Flat black version for small icons (including specific journals)

| more_settings =
| development_wiki = Not yet any separate technical-development wiki (e.g. in Wikimedia Labs)
| participants = Participants (editors, authors and peer reviewers) as of 2019-05-15
*'''Authors''': 172 ([[v:Template:Author_count|counting template]])
*'''Editorial boards'''': 62 ([[v:Template:Editor_count|counting template]])
*'''Associate editors''': 15 ([[v:Template:Editor_count|counting template]])
*'''Peer reviewers''': 70
*'''Additional on-wiki participants''': approx 5-10
'''Total''': approx 300-350
<br>[[Wikiversity:WikiJournal_User_Group/Editors|Editorial boards and associate editors]]
<br>[[WikiJournal_User_Group#Members_of_the_administrative_board|WikiJournal Admin board]]

Estimate of editors active in any given month:
*≥5 edits per month on-wiki: 25
*≥5 email to mailing lists: 25
*Monthly conference call meeting: 10
Notes: 1) a lot of work currently has to be done off-wiki. 2) Almost all peer reviewers only ever contribute once. 3) Many authors also only contribute once when depositing an article and once when responding to respond reviewer comments.

Readership from DOI-clicks in line with typical academic journals (800 per article).
{{Graph:Chart
| type = line
| width = 400
| height = 150
| xAxisTitle = 2018
| yAxisTitle = DOI resolutions per month
| x = Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov
| y = 1283,1312,1528,1289,1554,1970,1878,2036,4154,7780,12270
}}
}}

==Scenario==

# Many Wikipedia articles lack information (especially on complex topics)
#*Although [[w:wp:GA|GA]] and [[w:wp:FA|FA]] involve editorial review of content, there is little formal review from outside experts
#*Lack of quality images
#Lack of contributions from academic community
#*Wikipedia is often viewed with suspicion by academics
#*Academic authors often seek more recognition than provided in the history tab
#*Writing in Wikipedia is sufficiently unfamiliar to be a deterrent
#*Original research cannot be published on Wikipedia

==Possible solution==
The Wikipedia community and the academic community can be converged and unified through a journal initiative under the Wikimedia banner. The journals needs to adhere to international guidelines and standard procedures, in addition to being open-access and editable by all. WikiJournal can provide a prototype based on which journals for various themes and subjects can be built on.

This involves two broad aspects: The background structure and the journal contents.

===Background structure===
Background structure comprises:
* Journal policies: This can be customized based on the journal theme and subject, but would be common overall.
* Templates: Specific templates need to be designed for each journal. These templates would probably not be relevant to any other wikiproject.
* Technical parameters:
** Unlike other wikiprojects, the journal project calls for specialized logins as authors, editors and/or peer reviewers.
** We need to consider the possibility of one individual having multiple capacities, and the specific capacity being specified for an edit.
** Custom PDF-rendering facility.
** Possible on-wiki storage of confidential information (e.g. anon peer-reviewer identities).

===Journal contents===
* Anyone would be able to make a submission. Specification of legal name and contact details might be required.
* The submitted preprint contents would undergo a public peer-review by external experts and considered critically by an elected aditorial board before accepted into a journal's mainspace, or rejected.
* After acceptance, the editing capacities for the article would be restricted.
* A permalink in the form of [[W:Digital Object Identifier|Digital Object Identifier]] or DOI would be awarded to each article after publication.
* A citation format for academic publications would be specified.

==Present situation==
Three journals are currently published by the [[v:WikiJournal User Group|WikiJournal Publishing Group]]:

* [[v:WikiJournal of Medicine|''WikiJournal of Medicine'']] (est. 2014) for medicine and biomedicine (ISSN 2002-4436)
* [[v:WikiJournal of Science|''WikiJournal of Science'']] (est. 2018) for science, technology, engineering and mathematics (ISSN: 2470-6345)
* [[v:WikiJournal of Humanities|''WikiJournal of Humanities'']] (est. 2018) for humanities, arts, and social sciences (ISSN: 2639-5347)

WikiJMed was the original WikiJournal, and was the template for the subsequently established journals with broader scope (further info at [[v:WikiJournal of Medicine/About|WikiJournal of Medicine/About]]). Based on this initiative, WikiJSci (previously "Second Journal of Science") was developed in 2018 and was soon followed by WikiJHum. A composite [[WikiJournal User Group]] was formed in 2016 to overlook the development of such journals.

==Proposal==
A wiki that is open for everyone to contribute, at the same time with the features of scholarly journals in that the published works undergo independent peer-review by subject experts before publication. The authors are clearly credited at the top of their articles, making it more attractive for researchers and scholars to contribute. Articles are indexed and citable. Works may include images and reviews that are supported by secondary sources. Wikipedia and other Wikimedia sister projects can subsequently use material from these publications.

===Why separate Wikiproject===

* An internal [[Wikiversity:WikiJournal/Future as separate Wikimedia project|discussion]] revealed a consensus for a move to a separate Wikiproject.
* It calls for custom structure that would probably not be required by other Wikiprojects.
** Certain types of users would need to specify their real names and contact details.
** Login types might need to be specified.
** Custom templates.
* Better visibility and awareness. The current journals have limited viewership possibly due to lack of awareness across Wikimedia users.
* Grant requirements would follow a definite prototype.
* The scope is unique. This uniqueness needs to be identified.
** A separate link as another sister project will enhance its visibility to Wikimedia users would therefore enhance participation and impact.
* The scope does not exactly merge with:
** Wikiversity: Although there is partial overlap in relation to ''open research'', the scope of WikiJournal goes beyond that. ''Academic publications'' are not necessarily same as ''open academia'', ''open educational resources'' or ''learning projects''.
** Wikibooks: ''Academic publications'' are not necessarily same as ''open-content textbooks''.
** Wikipedia: Although Wikipedia is most read information source, it is often not given the credibility it deserves. While a few journals have started taking Wikipedia seriously, it still cannot claim the academic recognition that WikiJournal could claim.
* Impact metrics may not be applicable to any other wikiproject and may call for additional support from Wikimedia labs.
* Translation to other language wikis would call for standard protocols, unlike any other sister project.
* It is essential for journals to be enlisted in various databases and to follow various international protocols. A single repository for all such journals will help in minimising the problems of separate listing in such databases or central bodies.
* Established academic journals may set up spaces within such a project to implement similar reviews.

==Alternative proposals==
{{cot|Former proposals with similar scope|align=left|bg=#DDDDEE|border=0px|indent=10px;width:80%}}
*[[Wiki Scholarly Journals]]
*[[Wikiversity:Wikiversity:Journal of the future|Wikiversity:Journal of the future]]
*[[Wikisource:Wikisource:WikiProject Academic Papers|Wikisource:WikiProject Academic Papers]]
*[[Wikiversity:Wiki Journal]]
*[[Wikiversity:Portal:Wiki Scholar]]
*[[wikiversity:User:OpenScientist/Open_grant_writing/Encyclopaedia_of_original_research|Wikiversity:Encyclopaedia of original research]]
*[[strategy:Proposal:Journal_(A_peer-review_journal_to_allow/encourage_academics_to_write_Wikipedia_articles)|WikiStrategy:Journal]]
*[[Wikipedia Scientific Journal]]
{{cob}}
{{cot|Articles that mention the format|align=left|bg=#DDDDEE|border=0px|indent=10px;width:80%}}
* {{cite journal|last1=Masukume|first1=G|last2=Kipersztok|first2=L|last3=Das|first3=D|last4=Shafee|first4=T|last5=Laurent|first5=M|last6=Heilman|first6=J|title=Medical journals and Wikipedia: a global health matter|journal=The Lancet Global Health|date=November 2016|volume=4|issue=11|pages=e791|doi=10.1016/S2214-109X(16)30254-6|url=https://www.thelancet.com/journals/langlo/article/PIIS2214-109X(16)30254-6/fulltext}}
* {{Cite journal|last=Shafee|first=T|last2=Mietchen|first2=D|last3=Su|first3=A|date=August 2017|title=Academics can help shape Wikipedia|url=http://science.sciencemag.org/content/357/6351/557.2|journal=Science|volume=357|issue=6351|pages=557–558|doi=10.1126/science.aao0462}}
* {{Cite journal|last=Shafee|first=T|last2=Masukume|first2=G|last3=Kipersztok|first3=L|last4=Das|first4=D|last5=Häggström|first5=M|last6=Heilman|first6=J|date= August 2017|title=Evolution of Wikipedia’s medical content: past, present and future|url=http://jech.bmj.com/content/early/2017/08/24/jech-2016-208601|journal=JECH|doi=10.1136/jech-2016-208601|pmid=28847845}}
* {{Cite journal|url=https://www.hlinc.org.au/content/open-access/item/wikipedia-integrated-publishing-a-comparison-of-successful-models|title=Health Libraries - Wikipedia-integrated publishing: a comparison of successful models|publisher=Health inform.|volume=26 |issue=2|doi=10.13140/RG.2.2.27470.77129}}
* {{Cite journal|year=2017|title=WikiJournal of Medicine, the first Wikipedia-integrated academic journal|url=https://en.wikiversity.org/wiki/WikiJournal_of_Medicine/WikiJournal_of_Medicine,_the_first_Wikipedia-integrated_academic_journal|journal=WikiJournal of Medicine|volume=4|pages=|doi=10.15347/wjm/2017.001|last=Shafee|first =T|last2=Das|first2=D|last3=Masukume|first3=G|last4= Häggström|first4=M}}
* {{Cite journal|last=WikiJSci Editorial board|date=2018-06-01|title=The aims and scope of WikiJournal of Science|url=https://en.wikiversity.org/wiki/WikiJournal_of_Science/The_aims_and_scope_of_WikiJournal_of_Science|journal=WikiJournal of Science|language=en|volume=1|issue=1|pages=1|doi=10.15347/wjs/2018.001}}
{{cob}}
=== WikiJournal as a publishing house ===
'''WikiJournal as a publishing house''' I am a little confused about how a WikiJournal project would work: would other users be allowed to come along and edit already published research? Would it be like [http://www.scholarpedia.org/article/Main_Page Scholarpedia] where you need credentials? Rather than make a separate ''project'' as such, maybe "WikiJournal" could be a regularly-published periodical or a publishing imprint that has stable versions of articles that have been collaborated on at Wikiversity. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 18:13, 28 August 2016 (UTC)
:As summarized at [[Wikiversity:WikiJournal_of_Medicine/About#Structure|the structure of WikiJournal of Medicine]], anyone may edit pages, even published ones, but substantial edits to the main text of such articles would be reverted. Instead, users should then make a separate draft, and have that draft peer reviewed as well. Peer reviewers must be experts in the subject, but authors do not necessarily have to be. Collaborations at any site with a permitting license may be submitted. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 19:16, 2 September 2016 (UTC)

=== WikiJournal Public-Private-Versioning and Dynamic Paper Management in a Wiki ===
For a Journal the concept of '''[[Wikiversity:Public-Private-Versioning|Public-Private-Versioning]]''' could be used to facilitate a community based paper development (the community could contribute during the evolution of the paper - transparent history of the evolution of the paper, and private versions are created by a reviewing process (see [http://at6fui.weebly.com/open-community-approach.html Open Community Approach]).

Furthermore a KnitR-Backend or SageMath-Backend for Wikiversity papers can be used for statistical and/or numerical analysis of data for the paper (see '''[https://en.wikiversity.org/wiki/KnitR#Workflow_for_KnitR-Backend_for_in_Wikiversity.2FWikipedia KnitR in Wikiversity]''').
--[[User:Bert Niehaus|Bert Niehaus]] ([[User talk:Bert Niehaus|talk]]) 15:11, 11 August 2017 (UTC)
:Apologies for the delayed reply! I think the project would need some feedback on the best overall architecture to use behind the scenes (what can be done directly with mediawiki, and what can be third-party) so long as they interface well. One limitation we've had, for example, is that reviewers have to submit comments via a google form because there is not yet visualeditor in talkpages, and anonymous editors need to privately register their identity and affiliation with the editorial board. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 06:19, 1 June 2019 (UTC)

== Discussion ==

#{{Support}}. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 18:18, 21 August 2016 (UTC) Editor-in-chief, WikiJournal of Medicine
#'''Disagree with split''' I don't see why it's valuable to split this from WV--this is perfectly within its scope. In fact, it is one of the real triumphs of that project and splitting it off would probably be to the detriment of that site. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 21:52, 21 August 2016 (UTC)
#: Having Wikiversity lose WikiJournal might be a huge loss to you, [[User:Koavf|Justin]]. However, all's not lost for Wikiversity, and there is still hope for Wikiversity. Indeed, Wikiversity has English courses, like [[v:English as a second language]], most of which needs further improvements. Recently, I had to help one of users who utilized his <u>poor</u> English writing skills at English Wikipedia. To help him improve his English skills, I had to direct him to [[v:English]] and [[b:English]]. I received thanks for helping him. Therefore, Wikiversity may be needed for users who want to improve their English writing skills for English Wikipedia. Don't you think so? --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 05:44, 26 June 2017 (UTC); edited, 05:54, 26 June 2017 (UTC)
#::{{Ping|George Ho}} Honestly, it seems like your English is better in the months that I've seen you posting across WMF sites. I definitely believe that there is potential in Wikiversity but I just don't think this should split from it. We'll see how it goes. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 05:50, 26 June 2017 (UTC)
#::: Thanks for complimenting my English. ;) --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 05:54, 26 June 2017 (UTC)
#{{Support}} A journal needs specific tools. Having it as its own sister site would be ideal. [[User:Doc James|<span style="color:#0000f1">'''Doc James'''</span>]] ([[User talk:Doc James|talk]] · [[Special:Contributions/Doc James|contribs]] · [[Special:EmailUser/Doc James|email]]) 15:00, 22 August 2016 (UTC)
#::I continue to '''strongly support''' this project. This is an effective method of bringing in knowledge to our movement. This may also have potential for oral knowledge from indigenous peoples with a less robust publishing tradition.[[User:Doc James|<span style="color:#0000f1">'''Doc James'''</span>]] ([[User talk:Doc James|talk]] · [[Special:Contributions/Doc James|contribs]] · [[Special:EmailUser/Doc James|email]]) 11:24, 3 June 2019 (UTC)
#{{Support}} Very promising proposal --[[User:Athikhun.suw|Athikhun.suw]] ([[User talk:Athikhun.suw|talk]]) 00:52, 28 August 2016 (UTC)
#{{Support}} I agree with the split. I don't think it belongs with Wikiversity at all, which is for courses and curricula. It makes more sense to me, if anything, that it should be part of Wikibooks, as that is a place for publication of original scientific works. The process for a journal paper is different than a book however so I agree it should be separate. As for the project in general, I think the wiki approach to writing a scientific paper is potentially really great. I know PLOS has their own internal wiki for writing [http://collections.plos.org/topic-pages Topic Pages], which are review papers that are written and then eventually transferred to Wikipedia. Non-review papers, however, don't really make sense as part of Wikipedia, so it makes sense to develop them on their own wiki. [[User:Mvolz|Mvolz]] ([[User talk:Mvolz|talk]]) 17:44, 30 August 2016 (UTC)
#{{Support}} (finally after changing my mind three times: I never oppose a reasonable request if it has the support of the community --[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 23:06, 3 June 2019 (UTC))<s> '''Disagree with split''' (''Changed vote to '''neutral''' with the understanding that the real question is whether the wiki hosts confidential or "private" conversations'') <small>Original text:</small> Keep in mind that I speaking from the biased perspective of a [[v:Wikiversity:Custodianship|Wikiversity Custodian]] who is only marginally involved with this WikiJournal project. One reason Wikiversity would want to host the journals is that the software developed for WikiJournal could be useful on Wikiversity. An example of such software might include confidential communications between editors and referees that are held on-wiki (instead of on a remote user group). I have no idea whether Wikimedia is willing or even able to host such confidentiality, but it would also allow students and authors to collaborate privately. Also, Wikiversity would be interested in hosting student-run journals. I concede that the prospect of amateaurish student-journals might not be appealing to board members, and fully understand why the board might wish to separate from Wikiversity. If the board chooses to split, I will support that decision.</s> --[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 01:35, 3 September 2016 (UTC)
#:Confidential talks are currently held on a [https://groups.google.com Google Group], which can be used for students and authors even if WikiJournal is split from Wikiversity. Likewise, students have at least the same ability to start journals after a split. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 12:57, 3 September 2016 (UTC)
#::Allowing for confidential conversations on a Wikimedia sister-wiki would be a major departure from protocol. The wiki that does it will need an independent governing body for each journal or organization that uses it. Someday, it would be nice for universities, laboratories, and journals to have such capabilities. I am neutral about the current proposed split if the confidentality is not included: Without the confidentiality option, I see neither a reason for the split, nor any harm done by splitting away from Wikiversity. But if this new wiki is created with confidentiality options, it will likely recruit university and laboratory-based journals that wish to utilize this option. The question of whether to allow this confidentiality option is likely to go to the top levels of the Wikimedia corporation...Perhaps what we really need is for Google groups to host discussions in wikitext.--[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 19:03, 3 September 2016 (UTC)
#::{{ping|Mikael Häggström}} The private option is already availablae at '''https://wikiversity.miraheze.org/wiki/Main_Page'''--[[User:Guy vandegrift|Guy vandegrift]] ([[User talk:Guy vandegrift|talk]]) 16:46, 4 September 2016 (UTC)
#{{Support}} The scope is unique and can extend to a number of domains. Specific tools needed. Access rights need to be different. It is also important to have the option of certain pages not being publicly accessible such that press embargo for unpublished articles do not get violated and yet editors or peer reviewers get to work in wiki format. <font face="Segoe script">[[User:Diptanshu Das|'''<font color="#ff0000">D</font><font color="#ff6600">ip</font><font color="#009900">ta</font><font color="#0000ff">ns</font><font color="#6600cc">hu</font>''']][[User talk:Diptanshu Das|<sup>Talk</sup>]]</font> 12:21, 5 September 2016 (UTC)
#{{Support}} I definitely agree with this. If it does air how would the three statutes you mentioned be done? Would peer reviewer, editor, and author have different edit rights or be purely decorative, and would you have to apply for them? [[User:Iazyges|Iazyges]] ([[User talk:Iazyges|talk]]) 04:55, 6 September 2016 (UTC)
#:Good questions, [[User:Iazyges|Iazyges]]. I see no reason for editors to need any particular edit rights, and readers without any account should be able to edit too, [[Wikiversity:WikiJournal_of_Medicine/Editors#Editing_published_works|even published works under certain conditions]]. I think the author role is also rather decorative, since it's the quality of their works that matter. I think the peer reviewers should need to apply, so that we know they fulfill [[Wikiversity:WikiJournal_of_Medicine/Peer_reviewers#Criteria|the criteria]]. [[User:Mikael Häggström|Mikael Häggström]] ([[User talk:Mikael Häggström|talk]]) 18:55, 15 September 2016 (UTC)
#{{Support}} per DocJames--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 11:59, 6 September 2016 (UTC)
#{{Support}} Because an open access journal is very different from WV and WB. --[[User:Netha Hussain|Netha Hussain]] ([[User talk:Netha Hussain|talk]]) 09:03, 13 September 2016 (UTC)
#{{Support}} because I'm looking for a project like this to publish some ideas. --[[User:Sophivorus|Felipe]] ([[User talk:Sophivorus|talk]]) 16:29, 20 November 2016 (UTC)
#{{Support}} - If this happens, I can read well the promising journal articles by academics. Though I can't write well the stuff, I can be a good reader to this. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 22:20, 18 January 2017 (UTC)
#:{{comment|Belated post-vote comment}}: I recently read peer reviews on scholarly articles and was amazed by comments and responses. I am also intrigued by the peer review templates, like [[v:en:Template:editor's comments]] and [[v:en:Template:Response]]. I [https://en.wikiversity.org/w/index.php?title=Talk:Radiocarbon_dating&diff=prev&oldid=1787502 fixed] a usage error recently, so I wonder whether the project can adopt either the templates or some software similar to MediaWiki's Support Desk or something like Wikinews's Comments (like [[:n:en:Comments:Judge jails 'monstrous' London serial killer Stephen Port|this example]]). Honestly, I found the templates less convenient for peer reviews, so I figured that some discussion software would be a better improvement. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 09:34, 5 December 2017 (UTC)
#{{Support}} -[[User:Richard923888|Richard923888]] ([[User talk:Richard923888|talk]]) 15:39, 21 January 2017 (UTC)
#{{Support}} - there is no reason why a separate journal cannot continue to link with WV but there is immense potential that cannot be achieved by remaining a sub-project. <span style="color:#29AB87">[[User:Green Giant|Green Giant]]</span> ([[User talk:Green Giant|talk]]) 15:09, 15 April 2017 (UTC)
#{{Support}} - This proposal has evolved and improved significantly since first proposed in 2016. The flagship ''WikiJournal of Medicine'' exemplifies what the project can achieve (see [http://dx.doi.org/10.15347%2Fwjm%2F2017.001 2017 editorial]). Starting up within Wikiversity was useful to incubate the project and prove that such a novel format is even feasible. Becoming a sister project would further support the initiative by adding legitimacy, support, and extra control of sidebar contents etc. There would remain a strong focus on generation, improvement, peer-review and re-integration of high-quality content into other WMF projects (especially Wikipedia), and a WikiJournal sister project would maintain strong ties to the other projects. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 01:03, 18 April 2017 (UTC)
#:I should note for transparency that since my original support vote, I'm now Editor-in-Chief of WikiJournal of Science, and I chair the administration board. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 00:07, 4 June 2019 (UTC)
#{{Support}} Great proposal!--[[User:Kiril Simeonovski|Kiril Simeonovski]] ([[User talk:Kiril Simeonovski|talk]]) 06:52, 9 May 2017 (UTC)
#{{Support}} For reasons adequately described above. · · · [[User:Pbsouthwood|Peter (Southwood)]] [[User talk:Pbsouthwood|<sup>(talk)</sup>]]: 08:09, 9 May 2017 (UTC)
#{{Support}} Great proposal with value for the academic community. <b>~<i><font color="#07517C">[[User:SuperHamster|Super]]</font></i><font color="#6FA23B">[[User:SuperHamster|Hamster]]</font></b> <small>[[User talk:SuperHamster|Talk]] [[Special:Contributions/SuperHamster|Contribs]]</small> 17:00, 9 May 2017 (UTC)
#{{Support}} more than that it is exactly what i had in mind because the lack of open source credited material is recurrent fact on wikipedia and it will expand wikimedia scope. --[[Special:Contributions/167.63.49.24|167.63.49.24]] 02:52, 2 June 2017 (UTC)
#{{Support}} - Seems like a reasonable proposal, I don't see why it shouldn't at least be given a try. I think the challenge will mostly consist of getting experts in various fields to peer-review, but that's not impossible to do. [[User:InsaneHacker|InsaneHacker]] ([[User talk:InsaneHacker|talk]]) 06:27, 2 July 2017 (UTC)
#<s>{{oppose}} they don't need an entire sister project. It has to stay in [[v:|WV]].</s>this user voted 2x, therefore have struck one vote--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 15:29, 24 October 2017 (UTC)
#:{{strong oppose}} to separate login. Just add the obligation to fill an ''informations'' tab in ''Preferences'' to allow contributing [[User:CreativeC38|CreativeC38]] ([[User talk:CreativeC38|talk]]) 10:19, 6 July 2017 (UTC)
#::{{Ping|CreativeC38}} Why does it ''have'' to stay on WV? You don't think there's any merit whatsoever to having it as a separate site instead of a subpage on WV in terms of presentation, attracting experts etc.? [[User:InsaneHacker|InsaneHacker]] ([[User talk:InsaneHacker|talk]]) 00:24, 8 July 2017 (UTC)
#:: Also, the "oppose" and "strong oppose" vote [https://meta.wikimedia.org/w/index.php?title=WikiJournal&diff=16967843&oldid=16955738 are yours]. I'm informing readers to avoid misleads. BTW, sometimes you feel that Wikiversity won't be the same without WikiJournal. However, Wikiversity has been Wikiversity, especially without WikiJournal. Also, it has some good lessons for others to read, like [[v:English]]. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 03:48, 8 July 2017 (UTC)
#{{Support}} - I think it is to Wikiversity's detriment that WikiJournal find a separate home, however, it does seem to be a better approach for WikiJournal itself, and it should attract more users to the wiki community. I trust that WikiJournal will encourage academics to develop lessons and courses supporting their work at Wikiversity. -- [[User:Dave Braunschweig|Dave Braunschweig]] ([[User talk:Dave Braunschweig|talk]]) 21:49, 8 July 2017 (UTC)
#{{Support}} I think WikiJournal would have better chances to develop and to engage with expert communities if it were a sister project. --<font style="font-family:Monotype Corsiva; font-size:15px;"> [[User:Daniel Mietchen|Daniel Mietchen]] ([[User talk:Daniel Mietchen|talk]]) </font> 17:38, 31 August 2017 (UTC)
#{{Support}} I agree my previous speaker. Good point -- <span style="font-variant:small-caps">[[User:DerFussi|Der]][[User talk:DerFussi|Fussi]]</span> 06:12, 13 September 2017 (UTC)
#{{s}} Per others. -- [[User:Thennicke|Thennicke]] ([[User talk:Thennicke|talk]]) 23:23, 16 October 2017 (UTC)
#'''Comment''' I propose to lessen the requirement to first make the article available in wiki format. Consider my case: I wrote a book (i.e. a very long article) in PDF format (generated from LaTeX) with my original research in mathematics and make it publicly available under an open license. I have a trouble publishing it, because journals don't publish 380 pages articles and book publishers refuse to publish a book which is already available online. I want to allow me to submit the PDF file and be reviewed in WikiJournal project. Note that converting PDF into wiki markup would be a hard work, and this way it would be needed to update after each change in my book (e.g. when I add a solution of a conjecture or correct a typo). --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 23:44, 26 October 2017 (UTC)
#:{{re|VictorPorton}} We definitely hope to implement some easier ways of importing LaTeX, DOCX and PDF submissions on the [[v:WikiJournal Preprints|submissions page]]. That will likely require help from the WMF's dev team. Currently, the main conversion option is probably [http://pandoc.org Pandoc]. We have had people submit as docx files, and the journal editors have manually reformatted for wikimarkup, but that's not a scalable solution. Note that currently only Wiki.J.Med. is accepting original research, whist the other journals starting up are focusing on review articles (at least initially) since these are 'safer' options for building the journals early on. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 02:55, 27 October 2017 (UTC)
#::It seems that we will never (or at least in near 50 years) have a good automated conversion from LaTeX to wiki. I propose not to convert but to allow the author to upload a PDF file and publish in the wiki just a link to author's files, not the article itself in wiki markup. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 12:33, 27 October 2017 (UTC)
#::We also need some reasonable policy about updates of already published articles. For example arXiv allows to upload more than one version of an article. (This is especially important with articles building a theory rather than proving a single result.) We need it too. Probably every change should be peer reviewed. Or we can trust authors that they improve their materials over time not make it worse. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 12:39, 27 October 2017 (UTC)
#:::The downside of if we were to have only a pdf version and no wikimarkup version, is that it would make it hard to integrate material into other Wikimedia projects (one of the current main goals of the journals). However, this is not set in stone, so could change. As for multiple versions - I agree with the need for more specific guidelines (it happens not to have come up yet). In addition to the history tab record of all edits during drafting on the preprint server, my expectation is that anything that changes content of a published article would have to be re-reviewed to retain legitimacy. Indeed I can imagine that people could publish updated 'versions' of a review article, as already happens for textbooks. I'd suggest more in-depth discussion be on the main [[v:Talk:WikiJournal_User_Group|WikiJournal discussion page]]. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 13:51, 27 October 2017 (UTC)
#::::Anyway my book won't be completely copied to Wikipedia. So to convert the entire book and every its part into wiki markup format is just largely useless work. If we need to publish some part in a wiki, we can convert parts of the book or article on as-needed basis. --[[User:VictorPorton|VictorPorton]] ([[User talk:VictorPorton|talk]]) 22:03, 27 October 2017 (UTC)
#::::: Hello, [[User:VictorPorton|Victor]]. Here is [[v:en:WikiJournal Preprints]], which has instructions on sending PDF files via email and provides email address for those wanting to send PDF files. --[[User:George Ho|George Ho]] ([[User talk:George Ho|talk]]) 02:15, 29 October 2017 (UTC)
#{{Support}} This sounds like "a hidden gem 💎" situation where something good is hidden in something else, people who would be interested in this but otherwise not in the Wikiversity might be able to see this sooner if it weren't "hidden away". --[[User:Donald Trung|Donald Trung]] ([[User talk:Donald Trung|Talk 🤳🏻]]) ([[Steward requests/Global/2017-08#Global lock Donald Trung and sockpuppets|My global lock 😒🌏🔒]]) ([[Steward requests/Global/2017-09|My global unlock 😄🌏🔓]]) 11:44, 10 November 2017 (UTC)
#{{support}} Very important project. [[User:Ammarpad|Ammarpad]] ([[User talk:Ammarpad|talk]]) 14:45, 18 November 2017 (UTC)
#{{Support}} This proposal has a unique scope, and would have been the only WMF project to seem trustworthy for referencing by most of academics. In addition to the potential features listed on the top, this project would require much stricter internal procedures and hence Wikiversity does not fit in its current form. --[[User:Strange quark|Strange quark]] ([[User talk:Strange quark|talk]]) 13:30, 30 December 2017 (UTC)
#'''Support''' I'm ready to give a hand for french version of this sister project. [[User:Lionel Scheepmans|Lionel Scheepmans]] <sup><big>✉ </big> [[User talk:Lionel Scheepmans|Contact]]</sup> <sub>French native speaker, sorry for my [[w:dysorthography|dysorthography]]</sub> 20:28, 25 February 2018 (UTC)
#{{support}} [[User:NMaia|NMaia]] ([[User talk:NMaia|talk]]) 09:32, 26 March 2018 (UTC)
#'''question'''('''comment''') we have 26 signatures above plus journals which have been added[https://en.wikiversity.org/wiki/WikiJournal_of_Science] and [https://en.wikiversity.org/wiki/WikiJournal_of_Humanities] ...so where are we in terms of the process of this proposal?(how much longer)thank you--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 20:27, 11 September 2018 (UTC)
#*{{Re|Ozzie10aaaa}} yes, previously comment has been from people who happened to come across the page. The [[Sister Projects Committee#Current%20new%20project%20process|Sister Projects Committee]] suggested the gathering of contributor data and to make sure that people in different projects are aware of the proposal, so I have placed some notifications around a few areas in wikipedia, wikidata and mailing lists. [[User:Evolution_and_evolvability|T.Shafee(Evo﹠Evo)]]<sup>[[User talk:Evolution_and_evolvability|talk]]</sup> 09:31, 2 June 2019 (UTC)
#{{support}} [[User:Reboot01|Reboot01]] ([[User talk:Reboot01|talk]]) 13:47, April 25, 2019 (UTC)
#{{support}} Splitting it could really allow greater participation in WJ from outside stakeholders. [[User:StudiesWorld|StudiesWorld]] ([[User talk:StudiesWorld|talk]]) 10:20, 16 May 2019 (UTC)
#{{support}} interesting proposal and splitting can make the arrangements much better! '''--'''[[User:علاء |<font size="3" face="Script MT Bold" style="color:black;">Alaa</font> ]] [[User_talk:علاء |:)..!]] 04:29, 2 June 2019 (UTC)
#{{support}} as article author - (Michael Stear) [[Special:Contributions/131.172.248.203|131.172.248.203]] 04:30, 2 June 2019 (UTC) 
#{{support}} as article author - (Kholhring Lalchhandama) [[User:Chhandama|Chhandama]] ([[User talk:Chhandama|talk]]) 06:20, 2 June 2019 (UTC) 
#{{support}} - (Fiona Mackinnon) [[Special:Contributions/49.180.152.237|49.180.152.237]] 04:57, 2 June 2019 (UTC) 
#{{support}} - [[User:Learnerktm|Learnerktm]] ([[User talk:Learnerktm|talk]]) 06:23, 2 June 2019 (UTC) 
#{{support}} as article author - (Andrew Z. Colvin) [[User:Azcolvin429|Azcolvin429]] ([[User talk:Azcolvin429|talk]]) 06:35, 2 June 2019 (UTC) 
#{{support}} as article author - [[v:User:Tsirel|Boris Tsirelson]]. WikiJournal evidently is very different from (the rest of) Wikiversity. [[User:Tsirel|Tsirel]] ([[User talk:Tsirel|talk]]) 07:00, 2 June 2019 (UTC)
#{{support}} - as article author - other WV articles I've read have little to do with those of WJ. However, I can understand the concerns raised here[https://en.wikipedia.org/wiki/Wikipedia_talk:Featured_article_candidates#A_proposal_for_WikiJournals_to_become_a_new_sister_project]. [[User:Funk Monk|FunkMonk]] ([[User talk:FunkMonk|talk]]) 07:00, 2 June 2019 (UTC) 
#{{support}} as article author - (Abdulmutalab Musa) [[User:Laamiido|Laamiido]] ([[User talk:Laamiido|talk]]) 07:39, 2 June 2019 (UTC) 
# {{support}} as article reviewer - (Gregor Stiglic) [[Special:Contributions/100.8.28.171|100.8.28.171]] 10:18, 2 June 2019 (UTC) 
#{{support}} as article author - (Lauren Gawne) [[Special:Contributions/14.203.84.11|14.203.84.11]] 10:38, 2 June 2019 (UTC) 
#{{support}} as article author -(Ozzie Anis)--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 10:57, 2 June 2019 (UTC)
#{{support}} as article author - [[User:Andrew Dalby|Andrew Dalby]] ([[User talk:Andrew Dalby|talk]]) 11:15, 2 June 2019 (UTC)
#{{support}} as article author - I vote FOR WikiJournal to become a full 'Sister Project' of Wikipedia. (Deepesh Nagarajan) [[Special:Contributions/14.139.128.17|14.139.128.17]] 11:46, 2 June 2019 (UTC)
#{{support}} [[User:Dank|Dank]] ([[User talk:Dank|talk]]) 12:23, 2 June 2019 (UTC)
#{{s}} [[User:Richard Nevell|Richard Nevell]] ([[User talk:Richard Nevell|talk]]) 12:49, 2 June 2019 (UTC)
#{{support}} - [[User:FULBERT|FULBERT]] ([[User talk:FULBERT|talk]]) 13:02, 2 June 2019 (UTC) - For journals to be taken seriously as academic and peer-reviewed contributors to knowledge, they need to appear solid and independent. Wikiversity is a wonderful idea, though it is not as useful as a dedicated space for open, peer-reviewed journal work. I believe that having a dedicated project space may also allow for some dedicated resources and visibility. This is consistent with the Wikimedia strategy to become the essential infrastructure of the ecosystem of free knowledge through knowledge as a service and knowledge equity.
#{{support}} as article reviewer - Niclas Borinder [[Special:Contributions/81.227.107.149|81.227.107.149]] 13:37, 2 June 2019 (UTC)
#{{support}} We have some details to sort but yes, for the spirit of it all and for committing significant resources to advance this idea in the immediate future, I support. [[User:Bluerasberry|<span style="background:#cedff2;color:#11e">''' Blue Rasberry '''</span>]][[User talk:Bluerasberry|<span style="background:#cedff2;color:#11e">(talk)</span>]] 14:10, 2 June 2019 (UTC)
#{{support}} as article author - Dudley Miles. I have found the project valuable in getting reviews by academic experts to raise the standard of an article. [[User:Dudley Miles|Dudley Miles]] ([[User talk:Dudley Miles|talk]]) 14:18, 2 June 2019 (UTC)
#{{support}} - [[User:Jacknunn|Jacknunn]] ([[User talk:Jacknunn|talk]]) 14:30, 2 June 2019 (UTC) This project has huge potential to bring peer-review to Wikipedia and have clear integration into the most famous Wikimedia project. Wikiversity has huge potential - but to speak frankly, it is not a University- The Open University is, and was very ahead of its time and one day, Wikimedia might partner or create something similar under this name. For now, it is not a University, and so is confusing to people not intimately familiar with Wikimedia projects (99.9999% of humanity). Even if it were a proper University, most universities create separate affiliated publishing houses (https://en.wikipedia.org/wiki/List_of_university_presses). I think simplifying this project as much as possible - that is 'creating peer-reviewed Wikimedia content using the familiar publishing norms of established peer-reviewed journals' is a good start, one that Wikimedia can build on and improve in alignment with the founding principles of the foundation. Project S is coming, let's be ready to meet it with a great front end and and even better back one! :)
#{{support}} Thank you for this well thought-out proposal, which addresses many limitations that have been identified over the course of the last few years. There are great benefits in separate sister project status, and honestly I don't think WV is a very suitable place for the journals to remain at at this point. --[[User:Elmidae|Elmidae]] ([[User talk:Elmidae|talk]]) 14:40, 2 June 2019 (UTC)
#{{oppose}} Various "technical requirements" violate the [[Founding principles]], especially the second one. While I understand the reasons, I don't think that such a project should be part of the Wikimedia "wiki family"; academic publishing works primarily through the reputation of its authors and publishers while Wikimedia projects work mostly on the basis of the dedicated interest of number of editors (both casual, sporadic, one time and regular ones) irrespective of their qualifications and trying to put both of them together isn't going to work due to the culture contrast. [[User:Jo-Jo Eumerus|Jo-Jo Eumerus]] ([[User talk:Jo-Jo Eumerus|talk]], [[Special:CentralAuth/Jo-Jo Eumerus|contributions]]) 15:18, 2 June 2019 (UTC)
#*that 'culture contrast' has existed for many years, a journal of this nature would only be a positive...IMO--[[User:Ozzie10aaaa|Ozzie10aaaa]] ([[User talk:Ozzie10aaaa|talk]]) 16:12, 2 June 2019 (UTC)
#*:Yeah, and we've had problems with it. I don't disagree with the existence of such a project, I object to making it part of the Wikimedia family. [[User:Jo-Jo Eumerus|Jo-Jo Eumerus]] ([[User talk:Jo-Jo Eumerus|talk]], [[Special:CentralAuth/Jo-Jo Eumerus|contributions]]) 16:25, 2 June 2019 (UTC)
#{{oppose}}, per Jo-Jo Eumerus. - [[User:SchroCat|SchroCat]] ([[User talk:SchroCat|talk]]) 16:00, 2 June 2019 (UTC)
#{{support}} as article reviewer - Jennifer Dawson [[User:JenOttawa|JenOttawa]] ([[User talk:JenOttawa|talk]]) 16:05, 2 June 2019 (UTC) 
#{{support}} as a Wikijournal contributor. One of the reasons I support this is that a journal would let us go farther than writing for an encyclopedia. Often, Wikipedia policies such as [https://en.wikipedia.org/wiki/Wikipedia:No_original_research NOR (no original research)] hinders our ability to be academic. For example, the article I was honored to submit, [https://en.wikiversity.org/wiki/WikiJournal_of_Humanities/Themes_in_Maya_Angelou%27s_autobiographies Themes in Maya Angelou's autobiographies], isn't comprehensive because there are no sources to fill in some aspects of the topic. Although I'm not an academic expert, my experience as a WP editor of this article and others like it has made me into an expert about Dr. Angelou. I'd like to see the mission of the Wikijournal expand to allow original research, in order to expand the comprehensiveness of topics. In that way, we can improve upon the academic nature of WP and fill in the gaps imposed upon us by WP policies and procedures and the gaps that are out there in academic literature. [[User:Figureskatingfan|Figureskatingfan]] ([[User talk:Figureskatingfan|talk]]) 21:24, 2 June 2019 (UTC)
#::'''Comment''' Agree. The same problem with Wikipedia in the (quite far) topic - mathematics. Wikipedia's principle is "to inform, not teach/explain", but readers really need explanations and examples, which often leads to violations of the "no original research" norm, and frustration on both sides, readers and editors. WikiJournal is able to complement Wikipedia with explanations and examples using expertise. For example, my recent submission (explanatory essay) "[[v:WikiJournal Preprints/Can each number be specified by a finite text?]]". Wikiversity admits original research, but does not restrict it by peer refereeing, which is a completely different story. [[User:Tsirel|Tsirel]] ([[User talk:Tsirel|talk]]) 05:24, 3 June 2019 (UTC)
#{{support}} - (Tseenster) [[User:Tseenster|Tseenster]] ([[User talk:Tseenster|talk]]) 23:43, 2 June 2019 (UTC) 
# {{oppose}} primarily per Jo-Jo Eumerus, with the added caveat that according to [[mw:Template:Page security extension disclaimer]], {{tq|MediaWiki was not written to provide per-page access restrictions, and almost all hacks or patches promising to add them will likely have flaws somewhere}}, meaning that the technical requirements violate not only founding principles but also the very way the code for MediaWiki is designed. [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">has returned</sub>]] 00:39, 3 June 2019 (UTC)
#{{support}} - [[User:Benoit Rochon|Benoit Rochon]] ([[User talk:Benoit Rochon|talk]]) 01:36, 3 June 2019 (UTC)
#{{support}} - as one of the few new projects that I have seen that makes sense. This one just fits. [[User:Philippe|--Philippe]] ([[User talk:Philippe|talk]]) 01:59, 3 June 2019 (UTC)
#{{support}} - Wade Kelly [[User:Mrkellar|Mrkellar]] ([[User talk:Mrkellar|talk]]) 06:00, 3 June 2019 (UTC) 
#{{support}} - Steven Chang [[User:Gixibyte|Gixibyte]] ([[User talk:Gixibyte|talk]]) 06:40, 3 June 2019 (UTC)
#{{support}} - [[User:Rwatson1955|Rwatson1955]] ([[User talk:Rwatson1955|talk]]) 07:27, 3 June 2019 (UTC) 
#{{support}} as article author - (Ignacio López) [[User:Munguira|Munguira]] ([[User talk:Munguira|talk]]) 08:04, 3 June 2019 (UTC) 
#{{support}} [[User:Mardetanha|<font face="Rage Italic" size="4" style="color:#000000;color:black"><i>Mardetanha</i></font>]] <sup><span style="font-family:Italic;color:black">[[user_talk:Mardetanha|talk]]</span></sup> 09:08, 3 June 2019 (UTC)
#{{s}}.--[[User:Vulphere|<span style="background:#000000; color:white; padding:2px;">Vulp</span>]][[User talk:Vulphere|<span style="background:#00b700; color:white; padding:2px;">here</span>]] 09:24, 3 June 2019 (UTC)
#{{support}} - (Niall O’Mara) [[User:Ngdomara|Ngdomara]] ([[User talk:Ngdomara|talk]]) 09:57, 3 June 2019 (UTC)  support
# {{support}} as article reviewer - Herbert Haller
# {{s}} - this project has a lot of potential and it makes sense to give it the resources it needs to grow. [[User:Sic19|Simon Cobb]] ([[User:Sic19|Sic19]] ; [[User_talk:Sic19|talk page]]) 13:34, 3 June 2019 (UTC)
#{{support}} - Amy Fountain [[User:AmyFou|AmyFou]] ([[User talk:AmyFou|talk]]) 14:31, 3 June 2019 (UTC) 
#{{support}} - Arfon Smith [[Special:Contributions/128.177.88.206|128.177.88.206]] 14:50, 3 June 2019 (UTC) 
#{{question}} – I assume any new journals are going to incubate within this project, right? (I don't see us being equipped at Incubator to get involved.) [[User:StevenJ81|StevenJ81]] ([[User talk:StevenJ81|talk]]) 17:08, 3 June 2019 (UTC)
#{{support}} - This is a solid proposal with a healthy ecosystem of participants. Full-discloure, my wife among them. :) Opposing this based upon technical requirements is a distraction. People use tools other than MediaWiki everyday to support the movement. If we could, I'd rather folks use an open-source solution than have their work buried in some closed-source system owned by for-profit company. Besides, [[Community_health_initiative/Partial_blocks|partial blocks exist in MediaWiki]] and extending that to other use cases is a strength of a flexible open-source platform. Not to get too into the weeds, but it's also commented as "preferred", not a do-or-die requirement for success. These are smart people and I'm sure they can get it done. :) So again, technical fiddly-bits are a weak argument to oppose and I'd rather see us make a strong argument to support a burgeoning new project. [[User:Ckoerner|Ckoerner]] ([[User talk:Ckoerner|talk]]) 17:51, 3 June 2019 (UTC)
#{{support}} Yes, I find it helpful that wikijournal is it's own project sort of like how wikiversity is it's own project and not included into wikibooks. Wikijournal is a complex process and the peer review process isn't easy for an open project to do, yes, enwikiversity did a great job but I guess with more specific structure, it will be more conducive for academics to review journals which then will allow more growth. For this structure, I will hope it can be developed with wikiversity in mind (in some sense like OTRS can be shared with all projects - the tool and etc). I find it more useful for wikiversity to be solely focused in delivering modules, research and etc. Doing peer reviews and etc may be impossible for some wikiversities (mine homewiki is one of them at that moment). For where it is incubating, I will think maybe at enwikiversity at this moment. --[[User:Cohaf|Cohaf]] ([[User talk:Cohaf|talk]]) 17:54, 3 June 2019 (UTC)
#{{support}} Need I say more? [[User:TheAwesomeHwyh|TheAwesomeHwyh]] ([[User talk:TheAwesomeHwyh|talk]]) 19:55, 3 June 2019 (UTC)
#{{support}} Yes, they will run into a lot of technical problems, but why not try? ;D — ''[[User:Jeblad|Jeblad]]'' 20:16, 3 June 2019 (UTC)
#<s>{{question}} Will wiki contributors who are not scholars have an opportunity to contribute to the project? [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:29, 4 June 2019 (UTC)</s> I now understand better per [https://en.wikiversity.org/wiki/WikiJournal_User_Group/Editors WikiJournal/Editors]. I follow this with my vote below. [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:36, 4 June 2019 (UTC)
#{{support}} The project. [[User:SelfieCity|SelfieCity]] ([[User talk:SelfieCity|talk]]) 00:36, 4 June 2019 (UTC)
#{{support}}. Yes. This will contribute tremendously towards the open access movement. [[User:OhanaUnited|<b><font color="#0000FF">OhanaUnited</font></b>]][[User talk:OhanaUnited|<b><font color="green"><sup>Talk page</sup></font></b>]] 00:42, 4 June 2019 (UTC)
#{{s}}. Project makes sense. [[User:Hiàn|Hiàn]] ([[User talk:Hiàn#top|talk]]) 01:20, 4 June 2019 (UTC)
#{{comment}} ({{ping|Mikael Häggström}}) The name of the proposed sister should '''not''' use camel case; that is, it should be either "Wikijournal" or, perhaps, "Wikijournals" (following the pattern of "Wikibooks"). The existing sisters don't use [[w:camel case|camel case]]: Wikipedia, Wiktionary, Wikinews, Wikibooks, etc. --[[User:Pi zero|Pi zero]] ([[User talk:Pi zero|talk]]) 03:14, 4 June 2019 (UTC)
#{{support}} the scope of WikiJournal is clearly different to Wikipedia and will be a beneficial addition to the Wikimedia family as per above. [[User:DaGizza|DaGizza]] ([[User talk:DaGizza|talk]]) 03:35, 4 June 2019 (UTC)
#{{support}}. I approve of the Wikipedia project and participate in it to some extent (though much more at Wikivoyage and Wikimedia Commons). However, what Wikipedia expressly lacks is peer-reviewed articles by experts. A free journal site where people don't have to pay loads of money to read cutting-edge papers on medicine and various other topics is an exciting idea and would be a great addition to the Wikimedia family. [[User:Ikan Kekek|Ikan Kekek]] ([[User talk:Ikan Kekek|talk]]) 04:23, 4 June 2019 (UTC)
#{{support}} - Dr Katherine Firth, La Trobe University [[Special:Contributions/121.211.87.1|121.211.87.1]] 05:50, 4 June 2019 (UTC) 
#{{Strong support}} — Improving the world's access to science may be considered one of the most important contributions the Wikimedia Foundation could ever achieve. With that being said, Tom Reller, Vice President of Global Communications at [[en:Elsevier|Elsevier]] recently said: ''"[[en:Elsevier#Plan S|If you think that information should be free of charge, go to Wikipedia]]"''. Perhaps we should prove him right. — [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 06:48, 4 June 2019 (UTC)

Grants talk:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-11-15T23:54:37Z

Bryandamon: /* Approval */ Added response to adjusting date.

==Approval==
Hello [[User:Bryandamon|Bryandamon]] and [[User:MarkAHershberger|MarkAHershberger]] thank you for your patience as we processed your grant request. I am approving your proposal. I understand your initial start date is before this approval so please do let me know if you need to adjust the project start and end dates to reflect the delay in processing this grant. Best regards, [[User:WJifar (WMF)|WJifar (WMF)]] ([[User talk:WJifar (WMF)|talk]]) 07:33, 15 November 2018 (UTC)
: Thanks [[User:WJifar (WMF)|Woubzena]], we would like to adjust the start end dates to be safe, not sure if I can do that to the page or if it is considered "locked". Let me know if I can, otherwise we would like to update the start date to today (15 November 2018) and the end date to 31 January 2019. - [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 23:54, 15 November 2018 (UTC)

Grants:Processing/Rapid/New/Group

2018-11-15T22:54:52Z

Bryandamon: /* What to expect throughout your grant */ Readability changes.

Congratulations on your funded grant request! Please follow the instructions below and provide the requested information and documents needed to process your grant.

== Information and documents needed to process your grant ==
# '''Email rapidgrants{{@}}wikimedia.org'''. If you cannot view or have difficulty editing the pdf forms, you may provide the requested information in the body of your email instead of completing the pdf form.
# '''Use <code><nowiki>[Information requested] YOUR RAPID GRANT NAME</nowiki></code>''' in your email's subject line. This allows us to more easily identify your email, since we process many grants and receive emails from grantees throughout the life cycle for each grant.
# '''[[Grants:Grant information form#Grant information form for groups|Grant information form]]'''[a]: Provide information so that we list the correct information in your agreement.
# '''[[Grants:Grantee information form#Grantee information form for individuals and groups|Grantee information form]]'''[b] '''and identification documents'''<ref>We take your privacy seriously. If you prefer to send scans of your ID via GPG encryption or through another secure method that you are comfortable with, please let us know when you reply to this information request. We are happy to find a solution that works best with you.</ref>: Provide information '''and''' scanned copies of unexpired government-issued IDs for all persons with bank account access to grant funds, including the person or people signing your agreement.
# '''Bank document''': Provide a document from your bank showing who has access to the bank account where grant funds will be received and kept. We need this information to make sure WMF is complying with US regulations, and so it is required for all grantees. <br> The document should include the account number (last few digits is okay), all account signatories, and something that verifies the document is from your banking institution. <br> There are a number of ways to satisfy this request, but the most common document we receive are a bank letter signed by a bank representative or an email directly from the bank representative to us at grantsadmin{{@}}wikimedia.org.
# '''[[Grants:Bank information form#Bank information form for groups|Bank information form]]'''[c]: Provide your detailed bank information, including any country specific requirements (e.g. for India, IFSC; Brazil, CPF; UK, Sort Code + Acct# + IBAN, etc.) If your bank has specific wire instructions for receiving funds from a US bank, please provide those as well. <br> For groups, we also request a joint bank account be used for the grant. A single user account may be used if the account is solely used for the group's activities and there is at least one other person with authorized access to the bank account. We understand that countries may have different laws and practices so, if it is especially difficult to establish a joint bank account or to authorize another person to access an individual bank account, please let us know. We will work with you to find a solution.

== What to expect throughout your grant ==
#'''Grant agreement''': Once we receive the information and documents requested, we will review them, draft your agreement, and send it to you with a request for your signature.
#'''Payment''': Once we receive your signed agreement, we will provide you the details of when to expect your grant funds. Please note that there may be some grants that will be paid as a reimbursement after grant reporting is completed and all grant receipts have been received by WMF. Grantees typically know in advance if their grant will be paid at the completion of the grant.
#'''Confirmation''': Please email grantsadmin{{@}}wikimedia.org once you have received the wired funds. Or let us know if 7 business days have passed, and you've not received the funds sent.
#'''Reporting''': Your final report is due within 30 days of the completion date listed in your grant proposal and signed grant agreement. Reporting requirements and instructions are at: https://meta.wikimedia.org/wiki/Grants:Project/Rapid/Report

== Links to forms needed to process your grant ==
[a] [https://meta.wikimedia.org/wiki/Grants:Grant_information_form#Grant_information_form_for_groups https://meta.wikimedia.org/wiki/Grants:Grant information form#Grant information form for groups]

[b] [https://meta.wikimedia.org/wiki/Grants:Grantee_information_form#Grantee_information_form_for_individuals_and_groups https://meta.wikimedia.org/wiki/Grants:Grantee information form#Grantee information form for individuals and groups]

[c] [https://meta.wikimedia.org/wiki/Grants:Bank_information_form#Bank_information_form_for_groups https://meta.wikimedia.org/wiki/Grants:Bank information form#Bank information form for groups]

== Footnote ==

[[Category:WMF grants administration]]

Grants:Project/Rapid/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-09-06T23:46:29Z

Bryandamon: Bryandamon moved page Grants:Project/Rapid/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit to Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit: Added to affiliate subpage.

#REDIRECT [[Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit]]

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-09-06T23:46:29Z

<div style="float:right; width: 24em">
{{Probox

|status= proposed

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
We would like to request grant money to fund the incorporation and non-profit status of the [[MediaWiki Stakeholders' Group]] (#mwstake). Incorporating as a non-profit would allow easier and more transparent handling of conference financing. #mwstake is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki Conferences] (EMWCon).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings, the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMWCon 2019] conference and all future EMWCon conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMWCon] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

* Finally, we incorporate! <span style="color:#d30000; text-decoration:inherit">☠</span>[[User:MarkAHershberger|MarkAHershberger]]<span style="color:#d30000; text-decoration:inherit">☢</span>([[User_talk:MarkAHershberger|talk]])<span style="color:#d30000; text-decoration:inherit">☣</span> 14:57, 16 August 2018 (UTC)
* Good news! [[User:LexSMW|LexSMW]] ([[User talk:LexSMW|talk]]) 15:46, 16 August 2018 (UTC) ([https://mwstake.org/mwstake/wiki/User:Lex_Sulzer Background reasoning])
* [[User:CCicalese (WMF)|CCicalese (WMF)]] ([[User talk:CCicalese (WMF)|talk]]) 20:30, 16 August 2018 (UTC)
* MediaWiki is the foundation of numerous sources of knowledge both inside and outside of Wikimedia. The events organized and hosted by the Stakeholders' group are the only events focused on the needs of the latter group. Supporting their ability to continue to successfully put on the these events - and the other impact described in the proposal - is crucial to the healthy development of the open-source project. I've learned so much and created numerous relationships through this user group. Sponsoring this grant will increase the impact of a group that has done so much, with so little. [[User:Ckoerner|Ckoerner]] ([[User talk:Ckoerner|talk]]) 15:48, 17 August 2018 (UTC)
* I have benefited tremendously from the contacts and knowledge provided by the MediaWiki Stakeholders' Group and I'm looking forward to it benefiting others as well. [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 16:50, 18 August 2018 (UTC)
* I support the idea of incorporation for MWSTAKE. The third-party wiki community needs a focal point for resources and the means to harness the input and development activity of the enterprise users of MediaWiki. Mark and Bryan are motivated and committed to the cause. [[User:GregRundlett|GregRundlett]] ([[User talk:GregRundlett|talk]]) 12:44, 22 August 2018 (UTC)

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-18T16:50:49Z

Bryandamon: /* Endorsements */ Endorsed.

<div style="float:right; width: 24em">
{{Probox

|status= proposed

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
We would like to request grant money to fund the incorporation and non-profit status of the [[MediaWiki Stakeholders' Group]] (#mwstake). Incorporating as a non-profit would allow easier and more transparent handling of conference financing. #mwstake is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki Conferences] (EMWCon).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings, the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMWCon 2019] conference and all future EMWCon conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMWCon] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

* Finally, we incorporate! <span style="color:#d30000; text-decoration:inherit">☠</span>[[User:MarkAHershberger|MarkAHershberger]]<span style="color:#d30000; text-decoration:inherit">☢</span>([[User_talk:MarkAHershberger|talk]])<span style="color:#d30000; text-decoration:inherit">☣</span> 14:57, 16 August 2018 (UTC)
* Good news! [[User:LexSMW|LexSMW]] ([[User talk:LexSMW|talk]]) 15:46, 16 August 2018 (UTC) ([https://mwstake.org/mwstake/wiki/User:Lex_Sulzer Background reasoning])
* [[User:CCicalese (WMF)|CCicalese (WMF)]] ([[User talk:CCicalese (WMF)|talk]]) 20:30, 16 August 2018 (UTC)
* MediaWiki is the foundation of numerous sources of knowledge both inside and outside of Wikimedia. The events organized and hosted by the Stakeholders' group are the only events focused on the needs of the latter group. Supporting their ability to continue to successfully put on the these events - and the other impact described in the proposal - is crucial to the healthy development of the open-source project. I've learned so much and created numerous relationships through this user group. Sponsoring this grant will increase the impact of a group that has done so much, with so little. [[User:Ckoerner|Ckoerner]] ([[User talk:Ckoerner|talk]]) 15:48, 17 August 2018 (UTC)
* I have benefited tremendously from the contacts and knowledge provided by the MediaWiki Stakeholders' Group and I'm looking forward to it benefiting others as well. [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 16:50, 18 August 2018 (UTC)

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T23:49:47Z

Bryandamon: /* Impact */ Slight grammar.

<div style="float:right; width: 24em">
{{Probox

|status= proposed

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
We would like to request grant money to fund the incorporation and non-profit status of the [[MediaWiki Stakeholders' Group]] (#mwstake). Incorporating as a non-profit would allow easier and more transparent handling of conference financing. #mwstake is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki Conferences] (EMWCon).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings, the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMWCon 2019] conference and all future EMWCon conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMWCon] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T22:37:42Z

Bryandamon: Moved from draft to proposed.

<div style="float:right; width: 24em">
{{Probox

|status= proposed

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
We would like to request grant money to fund the incorporation and non-profit status of the [[MediaWiki Stakeholders' Group]] (#mwstake). Incorporating as a non-profit would allow easier and more transparent handling of conference financing. #mwstake is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki Conferences] (EMWCon).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMWCon 2019] conference and all future EMWCon conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMWCon] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T22:18:25Z

Bryandamon: /* Impact */ Updated EMW to EMWCon

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
We would like to request grant money to fund the incorporation and non-profit status of the [[MediaWiki Stakeholders' Group]] (#mwstake). Incorporating as a non-profit would allow easier and more transparent handling of conference financing. #mwstake is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki Conferences] (EMWCon).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMWCon 2019] conference and all future EMWCon conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMWCon] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T22:15:13Z

Bryandamon: /* Project Goal */ Removed section about dues.

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
We would like to request grant money to fund the incorporation and non-profit status of the [[MediaWiki Stakeholders' Group]] (#mwstake). Incorporating as a non-profit would allow easier and more transparent handling of conference financing. #mwstake is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki Conferences] (EMWCon).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMW 2019] conference and all future EMW conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T22:12:48Z

Bryandamon: /* Project Goal */ Brought the ask to the front.

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
We would like to request grant money to fund the incorporation and non-profit status of the [[MediaWiki Stakeholders' Group]] (#mwstake). Incorporating as a non-profit would allow easier and more transparent handling of conference financing. #mwstake is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki Conferences] (EMWCon).

In addition, there is an open discussion whether the entity would collect member dues, if so it would support the transparent collection and use (bug fixes, feature enhancements, documentation, etc.) of the dues.

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMW 2019] conference and all future EMW conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T22:06:41Z

Bryandamon: Removed misleading sentence.

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
The [[MediaWiki Stakeholders' Group]] (#mwstake) is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki conferences]. Incorporating as a non-profit would allow easier and more transparent handling of conference financing.

In addition, there is an open discussion whether the entity would collect member dues, if so it would support the transparent collection and use (bug fixes, feature enhancements, documentation, etc.) of the dues.

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMW 2019] conference and all future EMW conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T21:56:40Z

Bryandamon: /* Impact */ Added note about incorporation poll and responses.

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
The [[MediaWiki Stakeholders' Group]] (#mwstake) is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki conferences], however currently a member of #mwstake acts as the bankroll for the conferences until tickets are sold. Incorporating as a non-profit would allow easier and more transparent handling of conference financing.

In addition, there is an open discussion whether the entity would collect member dues, if so it would support the transparent collection and use (bug fixes, feature enhancements, documentation, etc.) of the dues.

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation during several group meetings the project goals above reflect a summary of the member responses.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMW 2019] conference and all future EMW conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T21:52:39Z

Bryandamon: Cleaned up grant proposal.

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (#mwstake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
The [[MediaWiki Stakeholders' Group]] (#mwstake) is [https://meta.wikimedia.org/wiki/Wikimedia_user_groups recognized] (MW-SG) by the Affiliations Committee and is involved every year with the [https://www.mediawiki.org/wiki/EMWCon Enterprise MediaWiki conferences], however currently a member of #mwstake acts as the bankroll for the conferences until tickets are sold. Incorporating as a non-profit would allow easier and more transparent handling of conference financing.

In addition, there is an open discussion whether the entity would collect member dues, if so it would support the transparent collection and use (bug fixes, feature enhancements, documentation, etc.) of the dues.

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimated to cost $1,500.

Once incorporated and after receiving non-profit status, #mwstake would inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar #mwstake meeting].

===Impact===
'''History of development'''<br>
The #mwstake Group polled it's members about the goals of incorporation and the results were collected.

'''Bank account for entity'''<br>
After the successful incorporation and non-profit status, #mwstake would use the corporations’ bank account to plan the logistics of the upcoming [https://www.mediawiki.org/wiki/EMWCon EMW 2019] conference and all future EMW conferences.

'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, #mwstake will be a nexus of support for MediaWiki users outside the Wikimedia sites. These users have a lot of experience, yet still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems and #mwstake aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside Wikimedia sites have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
<nowiki>#</nowiki>mwstake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. #mwstake wants to build a friendly environment for them to share their work and give them visibility. In addition, #mwstake wants to make it easier for people seeking professional services and support to be able to find quality help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. #mwstake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. #mwstake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, #mwstake wants to ensure the full utilization of the software on non-Wikimedia wikis. #mwstake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member
# Employ service of a legal counsel for the incorporation and non-profit creation process

'''Expenses'''
* $1,875 — Incorporation lawyer fees
* $125    — Pennsylvania Department of State incorporation fee & required legal notice publication

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T08:00:29Z

Bryandamon: Grammar is hard and added expense table.

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (MWStake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promotion of MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
The [[MediaWiki Stakeholders' Group]] (MWStake) 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. MWStake is involved every year with the [https://www.semantic-mediawiki.org/wiki/SMWCon SMW] and [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, however currently a member of MWStake acts as the bankroll for the conferences until tickets are sold. Incorporating as a non-profit would allow easier and more transparent handling of conference financing in addition to allowing the collection of membership dues and decision making on how to spend them (bug fixes, feature enhancements, documentation, etc.).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimates to cost $1,500.

The MWStake Group polled it's members about the goals of incorporation and the [https://mwstake.org/mwstake/wiki/MWStake_incorporation results were collected].

After the successful incorporation and non-profit status, MWStake will immediately inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar MWStake meeting] and then use the entity to plan the logistics of the upcoming [https://smw-cindykate.com/main/Community:Component0528678427 SMW 2019] and [https://www.mediawiki.org/wiki/EMWCon EMW 2019] conferences.

===Impact===
'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.semantic-mediawiki.org/wiki/SMWCon SMW] and [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, MWStake will be a nexus of support for MediaWiki users outside the Wikimedia sites. Users outside the WMF have a lot of experience. Still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems. MediaWiki Cooperation aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside WMF have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
MWStake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. MWStake wants to build a friendly environment for them to share their work and give them visibility. In addition, MWStake wants to make it easier for people seeking professional services and support to be able to find help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. Through the MediaWiki Cooperation, MWStake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. MWStake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, MWStake wants to ensure the full utilization of the software by on non-WMF wikis. MWStake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member and president
# Employ service of a legal counsel for the incorporation and non-profit creation process
#* We have already contacted a lawyer that Mark has used in the past and has experience with non-profit incorporation

'''Expenses'''
{| class="wikitable"
|-
! Cost !! Description !! Phase
|-
| $1,875 || Incorporation lawyer fees || This Phase
|-
| $125 || Pennsylvania Department of State incorporation fee & required legal notice publication || This Phase
|-
| $900 || IRS non-profit status lawyer fees || Next Phase
|-
| $600 || IRS non-profit filling fee || Next Phase
|}

== Endorsements ==

Grants:Project/Rapid/MW-SG/Legal fees for MediaWiki Stakeholders' Group incorporation as a non-profit

2018-08-15T07:40:35Z

Bryandamon: Draft version

<div style="float:right; width: 24em">
{{Probox

|status=draft

|grantee= Bryandamon

|contact= [[User:Bryandamon|Bryandamon]]

|project= MediaWiki Stakeholders' Group/incorporation as a non-profit

|affiliate= MW-SG

|summary= The [[MediaWiki Stakeholders' Group]] (MWStake) would like to incorporate and get non-profit status to more efficiently serve the needs of our diverse community through conferences, strategic development work (bug fixes, feature enhancements, documentation, etc.), and promote MediaWiki for 3rd party use.

|target= MediaWiki 3rd party use (developers, system administrators, consultants, hosting providers, and users)

|start_date= September 26

|start_year= 2018

|end_date= December 28

|end_year= 2018

|amount_local= $2,000

|amount= $2,000

|grant_type= Group

|organization= MediaWiki Stakeholders' Group

|contact2= [[User:MarkAHershberger|MarkAHershberger]]

|website= [[MediaWiki Stakeholders' Group]]

|nonprofit=

|portal=Rapid
|translations=Probox/Rapid/Content
}}

{{#ifexist: {{FULLPAGENAME}}/Report | {{Rapid/button/report-review}} | {{Rapid/button/report}} }}
</div></div>


==Project Goal==
The [[MediaWiki Stakeholders' Group]] (MWStake) 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. MWStake is involved every year with the [https://www.semantic-mediawiki.org/wiki/SMWCon SMW] and [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, however currently a member of MWStake acts as the bankroll for the conferences until tickets are sold. Incorporating as a non-profit would allow easier and more transparent handling of conference financing in addition to allowing the collection of membership dues and decision making on how to spend them (bug fixes, feature enhancements, documentation, etc.).

==Project Plan==


===Activities===
[[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward and will work directly with [[User:MarkAHershberger|Mark Hershberger]] to secure a lawyer to proceed with the incorporation (phase I) and then file for non-profit status with the IRS (phase II). All grant money will be used for lawyer and filing fees. The incorporation phase (this grant) is estimated to cost $2,000 and the non-profit filing (future rapid grant request) is estimates to cost $1,500.

The MWStake Group polled it's members about the goals of incorporation and the [https://mwstake.org/mwstake/wiki/MWStake_incorporation results were collected].

After the successful incorporation and non-profit status, MWStake will immediately inform it's members via email and during the next [https://mwstake.org/mwstake/wiki/Calendar MWStake meeting] and then use the entity to plan the logistics of the upcoming [https://smw-cindykate.com/main/Community:Component0528678427 SMW 2019] and [https://www.mediawiki.org/wiki/EMWCon EMW 2019] conferences.

===Impact===
'''Communication and coordination among MediaWiki users'''<br>
In addition to the [https://www.semantic-mediawiki.org/wiki/SMWCon SMW] and [https://www.mediawiki.org/wiki/EMWCon EMW] conferences, MWStake will be a nexus of support for MediaWiki users outside the Wikimedia sites. Users outside the WMF have a lot of experience. Still, there is a need to provide answers to their support questions. These users improve MediaWiki with extensions and share common problems. MediaWiki Cooperation aims to give them a voice to share their experience and coordinate their efforts.

'''Coordination between different groups of MediaWiki developers and operators'''<br>
Core changes can sometimes break widely used extensions, but they also have the potential to greatly improve widely used extensions. Extension developers find bugs, improve core code and simply rely on the core. Operators of wikis outside WMF have their own issues, but could greatly benefit from and contribute to the experience of people running the Wikimedia sites.

'''Foster the ecosystem around MediaWiki'''<br>
MWStake recognizes there is a range of developers, consultants, and companies that work with MediaWiki and improve functionality for their customers. MWStake wants to build a friendly environment for them to share their work and give them visibility. In addition, MWStake wants to make it easier for people seeking professional services and support to be able to find help.

'''Facilitate implementation of MediaWiki features'''<br>
There is a need for features that are not in the core focus of Wikimedia sites, but could greatly improve the user experience of other wikis. Through the MediaWiki Cooperation, MWStake aims to be able to support the development of these features.

'''Improve documentation of extensions and MediaWiki visibility'''<br>
The documentation of MediaWiki, especially its extensions, is a key success factor for its use outside of Wikimedia sites. MWStake aims to improve the quality of documentation and make it easier for outside users to assess the benefit and quality of extensions.

'''Contribute to the development of MediaWiki'''<br>
By watching the proposed changes to MediaWiki and assessing the impact to users outside of the Wikimedia sites, MWStake wants to ensure the full utilization of the software by on non-WMF wikis. MWStake will also commit to contributing our improvements and work towards their inclusion in the main product.

===Resources===
# [[User:Bryandamon|Bryan Hilderbrand]] will act as project manager to move the effort forward
# [[User:MarkAHershberger|Mark Hershberger]] will be the key decision maker and future board member and president
# Employ service of a legal counsel for the registration process
#* We have already contacted a lawyer that Mark has used in the past and has experience with non-profit incorporation

== Endorsements ==

User:Bryandamon

2018-08-15T07:00:26Z

Bryandamon: Added soft redirect.

Grants:Project/Rapid/MarkAHershberger/MABS: Multilateral, Asynchronous, Bidirectional Synchronisation (of wikis)

2018-05-14T21:12:52Z

Bryandamon: Endorsed by Bryandamon

<div style="float:right; width: 24em">
{{Probox|status=proposed|grantee=MarkAHershberger
|contact=MarkAHershberger
|project=Multilateral, Asynchronous, Bidirectional Synchronisation (of wikis)
|affiliate=|summary=Provide a MediaWiki extension that implements MABS as a proof of concept. This will let anyone without too much technical expertise see that the technology is capable of synchronizing edits across wikis.
|target=* (Every wiki has potential users whose internet access is limited or sporadic.)
|start_date=June 25
|start_year=2018
|end_date=August 31
|end_year=2018
|amount_local=2000USD
|amount=2000
|grant_type=individual
|organization=|contact2=|website=|nonprofit=|portal=Rapid|translations=Probox/Rapid/Content}}

{{#ifexist: {{FULLPAGENAME}}/Report|{{Rapid/button/report-review}}|{{Rapid/button/report}}}}
</div>


== Project Goal ==
We're trying to provide better ways to incorporate the work of editors who do not have reliable network access.

[http://www.wikifundi.org/ WikiFundi] has done the initial work of providing the editing experience to offline users, but incorporating their work back into Wikimedia projects is still a manual process.

[http://git-media.wiki/deck/site/light.html Multilateral, Asynchronous, Bidirectional Synchronisation (MABS)] is a method that is under development to provide a way to automate incorporating the edits into Wikimedia projects, but the the technology is not automated and has a steep learning curve.

== Project Plan ==


=== Activities ===
I, assisted by others of different technical levels, will work to develop and test an extension that will show that automating remote edit incorporation is a feasible goal.

At the end of the project, we plan to have an extension and sufficient documentation available so that interested parties (e.g. WikiFundi or [[mw:Asynchronous Wikis/2018 NASA JSC ICA Grant Proposal|astronauts on the ISS]]) can see that this is a viable solution to the problem.

Additionally, we hope to use the proof of concept to attract other developers of [[:en:FLOSS|FLOSS]] to the project and improve the viability of it over the long term.

=== Impact ===

# Number of total participants: 3 (myself and 2 assistants)
# Number of articles created or improved: n/a or (over the life of the tool) 1000s.
# Number of photos uploaded to Wikimedia Commons: n/a or (over the life of the tool) 100s.
# Number of photos used on Wikimedia projects: n/a or (over the life of the tool) 10s.

(''Note that content creation is not the target of this grant proposal, but this project will, if successful, enable many, many contributions over the long term.'')

=== Resources ===
I will be contributing my own time. This rapid grant will be used to pay for my assistants' time that they will spend testing, documenting, and helping me develop this tool.

I will use my involvement in the Wikimedia movement, my knowledge of MediaWiki, and my contacts with third party MediaWiki users and their use cases to implement and test this proof of concept.

Funding may become available from other sources once they see this proof of concept.

*
*
*

== Endorsements ==


* I totally agree with all the points above. This proof of concept will be beneficial to many projects including WikiFundi and NASA's goal of wikis in space. With a working prototype, we can consider how this might be included in these projects or inform the final product. It will help us kick off usability and design conversations. Also it will help us communicate and demonstrate the value of asynchronous wikis to less technical partners. This latter point will allow us to find other funding resources and ensure the larger project's completion. [[User:DStrine_(WMF)]]
*In order to truly have a MABS wiki system, I see two key technologies that need to be integrated with MediaWiki: The ability to synchronize more frequently with just the revised content (not the entire wiki as a whole each time) and the ability to resolve revision conflicts due to changes being synchronized bidirectionally. This prototype will help demonstrate these problems and how they can be solved. In my experience advocating for the use of wikis, a working prototype significantly helps to get the point across to non-technical audiences and increases the chance of support and funding. [[User:Darenwelsh|Darenwelsh]] ([[User talk:Darenwelsh|talk]]) 20:02, 11 May 2018 (UTC)
*This project has the potential to help in a variety of offline use cases. Before I joined the Foundation, I worked with customers who desired offline editing access. They wanted to be able to edit while in transit or in bandwidth limited environments and then have their edits synchronized to their wikis when they had connectivity. Mark has talked about this capability for a while, but has not had the time or resources to pursue a working prototype. This funding would help jump start this project and prove its feasibility. [[User:CCicalese (WMF)|CCicalese (WMF)]] ([[User talk:CCicalese (WMF)|talk]]) 15:27, 12 May 2018 (UTC)
* Besides being relevant to some groups who use MediaWiki for extremely high-impact knowledge sharing projects ([https://wikem.org/ WikiEm] for emergency medicine , [http://www.wikifundi.org/ WikiFundi] for Wikipedia editing in the global South, [https://blog.wikimedia.org/2016/05/05/mediawiki-nasa/ NASA EVA team] for space flight research), this experiment will be useful for two very important technical problems for the Wikimedia community: offline editing (see e.g. [[phab:T106898|T106898]]) and sharing JS/Lua/template code between wikis ([[phab:T121470|T121470]]). While we probably want to take a different approach for those, it will still be instructive to see how well this one works and what UX strengths and weaknesses it exposes. --[[User:Tgr (WMF)|Tgr (WMF)]] ([[User talk:Tgr (WMF)|talk]]) 07:48, 13 May 2018 (UTC)
* This project coincides with my own developing toolset at https://dataspects.com/structured-data-management-suite and I am looking forward to cooperating! [[User:LexSMW|Lex]]
*Synchronization of wikis could have positive impacts to remote users of wikis, as well as provide the opportunity to synchronize similar content between wikis. [[User:Jamesmontalvo3|Jamesmontalvo3]] ([[User talk:Jamesmontalvo3|talk]]) 15:06, 14 May 2018 (UTC)
*Bidirectional synchronization of wikis could be very useful for private wikis that would like to publish a limited amount of their content and solicit external (public) feedback (possibly via discussion pages). [[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 21:12, 14 May 2018 (UTC)

Grants:Project/Rapid/EMWConSpring2018/Video/Report

2018-04-30T20:27:06Z

Bryandamon: Removed section suggestions, added internal links, and removed individual first person perspective.

{{Rapid Grant report|Status=Under review|Date=2017-18|Grantee=individual|Type=Final}}

==Goals==
Our main goal was to provide quality videos of the conference. The group was extremely pleased with how the project went.

==Outcome==
{{Project/Rapid/Report/Table/Header1}}



{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Hold a three-day conference featuring discussions of topics related to "Enterprise MediaWiki", i.e. the usage of MediaWiki software by and within companies, non-profits, governments, and other organizations.
| achieved outcome = We held a very informative conference spanning three days of talks with about 35 attendees.
| explanation = Several employees/developers/administrators from NASA, General Electric, European Space Agency and smaller organizations attended. A few key WMF staff members helped organize, attended and spoke at the event - with Victoria Coleman providing a closing keynote presentation on Friday. The event also featured some of the top MediaWiki consultants - from North America and Europe.
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Further the [[Strategy/Wikimedia_movement/2017/Direction#Knowledge_as_a_service:_A_platform_that_serves_open_knowledge_to_the_world_across_interfaces_and_communities|WMF strategic goal of Knowledge as a Service]]
| achieved outcome = This is a long-term target, but we did achieve some notable progress in this direction.
| explanation = One of topics of discussion was the [[MW:Meza|Meza]] system [[MW:5 Year NASA Wikiversary|developed at NASA]]. Meza is an automated deployment system (based on Ansible) for creating fully functional wikis and wiki farms from zero. By providing full-fledged wikis in under an hour, it lowers the barriers of entry for MediaWiki in any environment, for any purpose. QualityBox founder Greg Rundlett takes it two steps further by providing hosting and commercial support for wikis - again making the MediaWiki system available as a "Platform As A Service" (PAAS). NASA is also working on solutions for synchronizing wikis between sites (ie. Earth and International Space Station). This would be an obvious achievement in organizing and exchanging free knowledge beyond Wikimedia. (The content can be used by all astronauts participating in the ISS program - regardless of country.)
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Improve the visibility of MediaWiki usage by third-parties
| achieved outcome = I think everyone involved received the message that MediaWiki is in use by a wide variety of industries and types of organizations.
| explanation = We had people talking about their usage of MediaWiki in the Oil and Gas industries; Geology; Manufacturing; Data and Finance; Space agencies; Government; Law and Legal; Technology consultants and contractors large and small.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Spread awareness of commercial support, regulatory certifications, and distributions (e.g. BlueSpice)
| achieved outcome = This was a focus of Greg Rundlett's talk on [https://www.youtube.com/watch?v=QpYOjSkQnN4&index=9&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh MediaWiki As A Service]. Sabine Melnicki talked about [https://www.youtube.com/watch?v=59MMWPSIuOk&index=18&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh MediaWiki and the European GDPR] Ben Fletcher talked about how the UK Ministry of Defense used MediaWiki for [https://www.youtube.com/watch?v=kZTMVC5K_Fk&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh&index=22 Delivering ICT capability] and Dr. Michael Barylak talked about [https://www.youtube.com/watch?v=ApnDvIkWTbs&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh&index=23 Comprehensive Quality Management] at the European Space Agency.
| explanation = We did spread awareness of the availability of commercial support. We had discussions about how MediaWiki hosting organizations '''meet''' regulatory certifications pertaining to security and privacy like SOC 2 ([[en:SSAE 16|SSAE 16]]), or the new [[en:General Data Protection Regulation|GDPR]] and also how MediaWiki is '''used''' in certification of standards for quality and management like [[en:ISO 9000|ISO 9000/9001]]. Distributions of MediaWiki like [[en:BlueSpice MediaWiki|BlueSpice]] from Hallo Welt! GmbH are typically those that have certified data centers, and have the tooling for doing intensive data collection and auditing (for obtaining certifications) and support the hosted distribution.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Recruit new organizations to adopt MediaWiki as a platform for enterprise knowledge
| achieved outcome = Unknown
| explanation = We are hoping to collect feedback from attendees<ref name="email"/> on whether the conference; or more specifically the videos, had any outcomes related to this goal.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Increase skills for existing editors, administrators, consultants and support organizations
| achieved outcome = Definitely!
| explanation = With a diverse audience, there were many "Aha!" moments where people learned new skills, methods, or possibilities of using the MediaWiki platform.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Recruit maintainers and contributors to extensions that are crucial to organizational use outside of WMF
| achieved outcome = Unknown
| explanation = We are collecting feedback from attendees<ref name="email">This was [https://equality-tech.com/civicrm/mailing/view?reset=1&id=81dafb233684be39 the message] distributed to each attendee</ref> on whether the videos had any outcomes related to this goal.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Add or improve content available at mediawiki.org
| achieved outcome = This outcome was indeed affected by the conference.
| explanation = I'm not so sure that it can be tied to the '''videos''', but Cindy Cicalese's contributions to Commons and the [https://commons.wikimedia.org/wiki/Special:Contributions/Legoktm video uploads by Kunal Mehta] definitely are. Yaron Koren was [https://www.mediawiki.org/w/index.php?title=Special:Contributions&offset=20180425235959&limit=500&contribs=user&target=Yaron+Koren&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 prolific] before and after the conference. James Montalvo III [https://www.mediawiki.org/w/index.php?limit=50&title=Special%3AContributions&contribs=user&target=Jamesmontalvo3&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 created a ton of new content on mediawiki.org] as a result of the conference. More contributions: [https://www.mediawiki.org/w/index.php?limit=50&title=Special%3AContributions&contribs=user&target=GregRundlett&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 GregRundlett], [https://www.mediawiki.org/w/index.php?limit=50&title=Special%3AContributions&contribs=user&target=Ckoerner&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 Ckoerner]

I created a program, and [https://tools.wmflabs.org/grantmetrics/programs/Content_contributions_flowing_from_EMWCon/EMWCon_2018_-_Houston,_TX event] using the Grant Metrics system on toollabs. I was able to identify 27 English Wikipedia users who participated in the conference. Unfortunately the Grant Metrics system only analyzes *.wikipedia.org sites, so it reports a limited amount of relevant content contributions that can be attributed to the conference or videos of the conference.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Provide quality videos of the conference which may be shared, re-used and built upon.
| achieved outcome = 25 Videos hosted on [https://www.youtube.com/watch?v=Umz5VwdYCn8&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh YouTube] and [https://commons.wikimedia.org/wiki/Category:EMWCon_Spring_2018 Commons] The YouTube channel has combined views of 2,661 as of the time of this report.
| explanation = The way that Carl Karsten of Next Day Video was able to provide a consistent look and feel to the videos was great. His process and tools were able to capture both the presenter and the screen as needed. Audo and Video quality was superb. Live streaming was provided at the last minute thanks to the push from Cindy Ciccalese. And if that wasn't good enough, the turn-around time was about 24 hours or less for these videos going up. I attended a conference the very next day which didn't have nearly the same results.
}}


{{PEG/Proposals/Reports/Final/Table/1/End}}

==Learning==
* '''What worked well?'''
*: Hiring a pro. We got exceptional results compared with the range of possibilities - including DIY or no video. By using online chat channels like Slack, Telegram and Matrix, we were able to coordinate things between organizers, facilities, and Carl. Using the event page on wiki worked really well to plan, outline, and then provide updates and details as the project progressed.
* '''What did not work so well?'''
*: The logistics were a bit complicated, and we definitely could have prepared earlier to make it even smoother.
* '''What would you do differently next time?'''
*: Although we had live streaming, we didn't plan for it. We should plan for it, and publicize it well in advance to attract a live online audience to the conference.

==Finances==

===Grant funds spent===
Next Day Video normally charges $9500 for a three-day conference. We contacted them early, and were offered a steep discount as a Free Software and Free Knowledge organization. We spent the entire grant of $2,050 - This amount at least offsets the hard costs of travel and lodging; with about $1,000 going towards producing videos of the conference.

===Remaining funds===
There were no remaining grant funds.



==Anything else==
''Anything else you want to share about your project?''

[[Category:Project/Rapid/Report]]

Grants:Project/Rapid/EMWConSpring2018/Video/Report

2018-04-30T19:48:08Z

Bryandamon: /* Learning */ Edited for readability and removed individual first person perspective.

{{Rapid Grant report|Status=Under review|Date=2017-18|Grantee=individual|Type=Final}}

==Goals==
''Did you meet your goals? Are you happy with how the project went?''

Our main goal was to provide quality videos of the conference. I am extremely pleased with how the project went.

==Outcome==
''Please report on your original project targets.''

{{Project/Rapid/Report/Table/Header1}}



{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Hold a three-day conference featuring discussions of topics related to "Enterprise MediaWiki", i.e. the usage of MediaWiki software by and within companies, non-profits, governments, and other organizations.
| achieved outcome = We held a very informative conference spanning three days of talks with about 35 attendees.
| explanation = Several employees/developers/administrators from NASA, General Electric, European Space Agency and smaller organizations attended. A few key WMF staff members helped organize, attended and spoke at the event - with Victoria Coleman providing a closing keynote presentation on Friday. The event also featured some of the top MediaWiki consultants - from North America and Europe.
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Further the [[Strategy/Wikimedia_movement/2017/Direction#Knowledge_as_a_service:_A_platform_that_serves_open_knowledge_to_the_world_across_interfaces_and_communities|WMF strategic goal of Knowledge as a Service]]
| achieved outcome = This is a long-term target, but we did achieve some notable progress in this direction.
| explanation = One of topics of discussion was the Meza system developed at NASA. Meza is an automated deployment system (based on Ansible) for creating fully functional wikis and wiki farms from zero. By providing full-fledged wikis in under an hour, it lowers the barriers of entry for MediaWiki in any environment, for any purpose. QualityBox founder Greg Rundlett takes it two steps further by providing hosting and commercial support for wikis - again making the MediaWiki system available as a "Platform As A Service" (PAAS). NASA is also working on solutions for synchronizing wikis between sites (ie. Earth and International Space Station). This would be an obvious achievement in organizing and exchanging free knowledge beyond Wikimedia. (The content can be used by all astronauts participating in the ISS program - regardless of country.)
}}

{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Improve the visibility of MediaWiki usage by third-parties
| achieved outcome = I think everyone involved received the message that MediaWiki is in use by a wide variety of industries and types of organizations.
| explanation = We had people talking about their usage of MediaWiki in the Oil and Gas industries; Geology; Manufacturing; Data and Finance; Space agencies; Government; Law and Legal; Technology consultants and contractors large and small.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Spread awareness of commercial support, regulatory certifications, and distributions (e.g. BlueSpice)
| achieved outcome = This was a focus of Greg Rundlett's talk on [https://www.youtube.com/watch?v=QpYOjSkQnN4&index=9&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh MediaWiki As A Service]. Sabine Melnicki talked about [https://www.youtube.com/watch?v=59MMWPSIuOk&index=18&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh MediaWiki and the European GDPR] Ben Fletcher talked about how the UK Ministry of Defense used MediaWiki for [https://www.youtube.com/watch?v=kZTMVC5K_Fk&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh&index=22 Delivering ICT capability] and Dr. Michael Barylak talked about [https://www.youtube.com/watch?v=ApnDvIkWTbs&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh&index=23 Comprehensive Quality Management] at the European Space Agency.
| explanation = We did spread awareness of the availability of commercial support. We had discussions about how MediaWiki hosting organizations '''meet''' regulatory certifications pertaining to security and privacy like SOC 2 ([https://en.wikipedia.org/wiki/SSAE_16 SSAE 16]), or the new [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation GDPR] and also how MediaWiki is '''used''' in certification of standards for quality and management like [https://en.wikipedia.org/wiki/ISO_9000 ISO 9000], ISO 9001. Distributions of MediaWiki like [https://en.wikipedia.org/wiki/BlueSpice_MediaWiki BlueSpice] from Hallo Welt! GmbH are typically those that have certified data centers, and have the tooling for doing intensive data collection and auditing (for obtaining certifications) and support the hosted distribution.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Recruit new organizations to adopt MediaWiki as a platform for enterprise knowledge
| achieved outcome = Unknown
| explanation = I'm hoping to collect feedback from attendees<ref name="email"/> on whether the conference; or more specifically the videos, had any outcomes related to this goal.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Increase skills for existing editors, administrators, consultants and support organizations
| achieved outcome = Definitely!
| explanation = With a diverse audience, there were many "Aha!" moments where people learned new skills, methods, or possibilities of using the MediaWiki platform.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Recruit maintainers and contributors to extensions that are crucial to organizational use outside of WMF
| achieved outcome = Unknown
| explanation = I'm hoping to collect feedback from attendees<ref name="email">This was [https://equality-tech.com/civicrm/mailing/view?reset=1&id=81dafb233684be39 the message] distributed to each attendee</ref> on whether the videos had any outcomes related to this goal.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Add or improve content available at mediawiki.org
| achieved outcome = This outcome was indeed affected by the conference.
| explanation = I'm not so sure that it can be tied to the '''videos''', but Cindy Cicalese's contributions to Commons and the [https://commons.wikimedia.org/wiki/Special:Contributions/Legoktm video uploads by Kunal Mehta] definitely are. Yaron Koren was [https://www.mediawiki.org/w/index.php?title=Special:Contributions&offset=20180425235959&limit=500&contribs=user&target=Yaron+Koren&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 prolific] before and after the conference. James Montalvo III [https://www.mediawiki.org/w/index.php?limit=50&title=Special%3AContributions&contribs=user&target=Jamesmontalvo3&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 created a ton of new content on mediawiki.org] as a result of the conference. More contributions: [https://www.mediawiki.org/w/index.php?limit=50&title=Special%3AContributions&contribs=user&target=GregRundlett&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 GregRundlett], [https://www.mediawiki.org/w/index.php?limit=50&title=Special%3AContributions&contribs=user&target=Ckoerner&namespace=&tagfilter=&start=2018-02-21&end=2018-04-25 Ckoerner]

I created a program, and [https://tools.wmflabs.org/grantmetrics/programs/Content_contributions_flowing_from_EMWCon/EMWCon_2018_-_Houston,_TX event] using the Grant Metrics system on toollabs. I was able to identify 27 English Wikipedia users who participated in the conference. Unfortunately the Grant Metrics system only analyzes *.wikipedia.org sites, so it reports a limited amount of relevant content contributions that can be attributed to the conference or videos of the conference.
}}
{{PEG/Proposals/Reports/Final/Table/1/Row
| target outcome = Provide quality videos of the conference which may be shared, re-used and built upon.
| achieved outcome = 25 Videos hosted on [https://www.youtube.com/watch?v=Umz5VwdYCn8&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh YouTube] and [https://commons.wikimedia.org/wiki/Category:EMWCon_Spring_2018 Commons] The YouTube channel has combined views of 2,661 as of the time of this report.
| explanation = The way that Carl Karsten of Next Day Video was able to provide a consistent look and feel to the videos was great. His process and tools were able to capture both the presenter and the screen as needed. Audo and Video quality was superb. Live streaming was provided at the last minute thanks to the push from Cindy Ciccalese. And if that wasn't good enough, the turn-around time was about 24 hours or less for these videos going up. I attended a conference the very next day which didn't have nearly the same results.
}}


{{PEG/Proposals/Reports/Final/Table/1/End}}

==Learning==
''Projects do not always go according to plan. Sharing what you learned can help you and others plan similar projects in the future. Help the movement learn from your experience by answering the following questions:''
* '''What worked well?'''
*: Hiring a pro. We got exceptional results compared with the range of possibilities - including DIY or no video. By using online chat channels like Slack, Telegram and Matrix, we were able to coordinate things between organizers, facilities, and Carl. Using the event page on wiki worked really well to plan, outline, and then provide updates and details as the project progressed.
* '''What did not work so well?'''
*: The logistics were a bit complicated, and we definitely could have prepared earlier to make it even smoother.
* '''What would you do differently next time?'''
*: Although we had live streaming, we didn't plan for it. We should plan for it, and publicize it well in advance to attract a live online audience to the conference.

==Finances==

===Grant funds spent===
''Please describe how much grant money you spent for approved expenses, and tell us what you spent it on.
Next Day Video normally charges $9500 for a three-day conference. We contacted them early, and were offered a steep discount as a Free Software and Free Knowledge organization. We spent the entire grant of $2,050 - This amount at least offsets the hard costs of travel and lodging; with about $1,000 going towards producing videos of the conference.

===Remaining funds===
''Do you have any remaining grant funds?''
No



==Anything else==
''Anything else you want to share about your project?''

[[Category:Project/Rapid/Report]]

User:Bryandamon

2018-03-02T16:21:01Z

Bryandamon: Created page with "This is Bryan Hilderbrand"

This is Bryan Hilderbrand