Page MenuHomePhabricator

Creation of a "Campaign" Wiki - initiatives.wikimedia.org
Closed, DeclinedPublic

Description

The idea for a programmatic wiki stemmed from conversations with the Wiki Loves Monuments team in Como in 2017. Meta.wiki or WikiCommons and other projects in terms of design at the time were greatly limiting. While the situation greatly improved through the introduction of Template Styles, there remains a lack of jquery and javascript available for usage in pages or hosting of third party content. Landing pages also get lumbered with the distracting miscellany of links and no option to style the broader MediaWiki interface.

Throughout the Thank You Campaign in 2019 of this year and throughout all the EU Copyright Directive community actions, it became clear that the Wikimedia Movement fundamentally lacks a clear location to host engaging content in a setting that gives us the flexibility and functionality as well as the ability to utilise at a moments notice.

INITIATIVES.WIKIMEDIA.ORG aims to provide a suitable location to host landing pages similar in options and capability to donate.wikimedia.org.

An external website:

  • Meta or other project
  • Foundation Website
  • DonateWiki
  • Bespoke wiki built as needed.

EXISTING OPTIONS AND LIMITATIONS

  • Toolforge - Unsuitable from a domain perspective.
  • Meta.wiki - Has template styles. Doesn’t allow RawHTML and access is too broad.
  • Donate.wiki - Meets most criteria but is a highly sensitive wiki due to its fundamental role within the fundraising pipeline. The wiki should be kept dedicated to the donation flow and shouldn’t have broader access or multiple uses for security reasons.
  • Payments.wiki - Where actions require tie in directly to the payments flow (like explicit repermissioning) then it makes sense to utilise Payments but beyond that simply isn’t appropriate.
  • foundation.wiki - now more a document storage wiki and not really suited for this purpose and also doesn’t have rawhtml.
  • wikimediafoundation.org - The Wikimedia foundation website whilst blessed with the rapid publication commons with wordpress sites, the annual report this year has indicated that it's restrictive from a design perspective and lacks extensive multilingual capabilities for the near and mid-term future.
  • people.wikimedia.org - Not suitable.
  • External websites - Wordpress has it’s uses but the wikimediafoundation.org website has shown the limitation presented by wordpress. Adaptability is limited and translation of content is currently non-existent. Multiple CTA’s are a challenge. Have their uses but doesn’t meet the above requirements.
  • Bespoke wiki’s such as fixcopyright.wikimedia.org - These wikis have their purposes but fixcopyright.wikimedia.org showed the challenges faced in a fast paced multilingual online campaign. Process and planning will solve some forthcomings but creating a wiki for every project is not a long term solution.

The suggestion is therefore create a wiki purely for programmatic online campaigns.

Requirements:

  • RawHTML
  • FundraisingLandingPage (See: T167374)
  • Publicly viewable.
  • Tied into SUL
  • Ability to edit only permitted based on permissions afforded on wiki.
  • Publicly viewable.
  • 2FA enabled.

Event Timeline

@Jseddon this would be a task for the regular ops team (not even fr-tech ops)

Urbanecm triaged this task as Low priority.
Urbanecm subscribed.

If I can take this as internally approved, I'll do the preparation stuff. What should be the wiki domain name? campaigns.wikimedia.org?

Dzahn edited projects, added Wiki-Setup; removed Wiki-Setup (Create).
Dzahn subscribed.
Urbanecm changed the task status from Open to Stalled.Oct 28 2018, 9:38 AM
Urbanecm removed Urbanecm as the assignee of this task.

Looks like stalled per @Dzahn's actions.

No no, don't get me wrong. We are just referencing each other. I did those actions when trying to help clean up the work board and after i saw your question wasn't answered yet.

So it is "user input needed" and can't be created yet simply because the name hasn't been decided yet.

I know nothing about the status beyond that.

@Jseddon Is this still requested? Did you want this to be called campaigns.wikimedia.org ?

Ah, thank you for your clarification @Dzahn.

Jseddon renamed this task from Creation of a "Campaign" Wiki to Creation of a "Campaign" Wiki - initiatives.wikimedia.org.Apr 3 2019, 1:41 PM
Jseddon updated the task description. (Show Details)
Jseddon updated the task description. (Show Details)

What should be the wiki domain name? campaigns.wikimedia.org?

I assume what's requested is now "initiatives.wikimedia.org" per the ticket title. Is that right, @Jseddon ?

Urbanecm changed the task status from Stalled to Open.Apr 17 2019, 7:15 AM
Urbanecm claimed this task.
Urbanecm moved this task from Blocked on others to Working on on the User-Urbanecm board.

In that case, I'm going to prepare initial configuration.

Change 504502 had a related patch set uploaded (by Urbanecm; owner: Urbanecm):
[operations/mediawiki-config@master] Prepare initial configuration for iniciativeswiki

https://gerrit.wikimedia.org/r/504502

Change 504503 had a related patch set uploaded (by Urbanecm; owner: Urbanecm):
[operations/dns@master] Add DNS entries for iniciativeswiki

https://gerrit.wikimedia.org/r/504503

Few comments on requirements:

Requirements:

  • RawHTML

Ok

  • FundraisingLandingPage (See: T167374)

Ok

  • Publicly viewable.

See below.

  • Tied into SUL

See below.

  • Ability to edit only permitted based on permissions afforded on wiki.

What does this mean? You want to grant edit permission only to certain users? Together with "publicly viewable" requirement, this usually means a fishbowl wiki is required. However, fishbowl wikis are non-SUL by definition, since granting edit permission is done by creating an account (revocation=blocking). If you need, for some reason I don't see right now, a fishbowl wiki tied into SUL, that should be technically possible, but I don't see the reasons.

  • 2FA enabled.

For everyone? Or privileged groups as usually?

@Urbanecm I assume that the reasoning is that anyone should be able to read the campaigns, but only specific users should be able to edit them, and those users would like to be able to use the same account that they normally use (SUL). A configuration solution for a "fishbowl wiki tied into SUL" could be that the user group not have the edit right, and instead restrict editing to a separate editors user group, meaning that granting edit permission would be separate from the account creation process.

That's...quite non-standard. It would require not placing the wiki to fishbowl.dblist (that would untie the wiki from SUL). I'd rather have some kind of approval if this is requested "just" because of this reason.

Well I'm not at all involved with this request - I just wanted to share a potential solution. I have no idea if this is indeed the reason.

@Jseddon Will this mean fixcopyright.wikimedia.org gets sunset and redirects to something within this new wiki?

Urbanecm moved this task from Working on to Blocked on others on the User-Urbanecm board.

Change 504503 merged by Dzahn:
[operations/dns@master] Add DNS entries for initiativeswiki

https://gerrit.wikimedia.org/r/504503

Mentioned in SAL (#wikimedia-operations) [2019-04-24T00:08:55Z] <mutante> DNS - add initiatives.wikimedia.org (and initiaves.m) for campaign wiki requested at T167375

@Jseddon Is this currently stalled on your end?

Change 504502 abandoned by Urbanecm:
Prepare initial configuration for initiativeswiki

https://gerrit.wikimedia.org/r/504502

@Jseddon Is this currently stalled on your end?

Doesn't seem like it's needed anymore. If it is, please reopen.

@Dzahn & @Urbanecm hey both. Picking this back up again.

Are we good to move forward with this?

Sure, if you still wish to have the wiki :). Could you please clarify what should the config look like? Thanks.

No answer to the questions asked: doesn't look it's needed anymore. Closing. If it is needed, feel free to reopen (and clarify the requirements, see questions asked in the ticket history).