[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Liam Wyatt]

Followup:
As previously mentioned, the public conversation "office hours" for the
Wikimedia Enterprise API project's *2022 Financial report & product
update, *was held yesterday.

For those who were interested but unable to attend, a recording of this
1h40m meeting - including timecodes for all questions/topics discussed - is
now available on on Commons and embedded in the project's talkpage:
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Enterprise#February_2023_Community_conversation_focusing_on_the_finance_report

Thank you to all who participated.

* Liam Wyatt [Wittylama]*

Senior Program Manager
for *Enterprise,* *Campaigns, & WikiCite*
Wikimedia Foundation


On Wed, 8 Feb 2023 at 14:21, Liam Wyatt  wrote:

> Hello Sam, thank you for the kind words.
>
> And also thank you to Chris and Martin for yours.
>
>
> With regards to the “optimizations” mentioned in the product update: usage
> change over the course of 2022 wasn’t really the motivating factor here
> (given it’s only been one year so we’re fully expecting fluctuations), It’s
> more about trying to increase the system’s efficiency and limit areas where
> things could break at scale - in preparation for future demand. There has
> been some increase in costs over the 2022 calendar year, as shown in the
> finance report’s bar-graph and associated paragraph, but that was primarily
> due to staffing changes, not hosting costs.
>
> Our initial system architecture focused heavily on Wikipedia database
> dumps and now we’re focusing on expanding the “realtime” data feeds. We
> decided to rebuild the architecture to look more like an event-based
> system, to work alongside exported-data products, instead of adding on more
> services on top of the dump generation.
>
> As mentioned in the product update, for those interested in this topic
> there are quarterly summaries of the technical work on the project’s
> MediaWiki page:
> https://www.mediawiki.org/wiki/Wikimedia_Enterprise#Updates But, if you’d
> like to talk through the implementation details and the thinking behind it,
> then the best format is a real-time conversation. I encourage you to come
> to the “office hours” public meeting this Friday - etails at the top of the
> project page on Meta. Even if you can’t make it to that, we’ll make sure to
> discuss the product update and I’ll be uploading the recording afterwards
> to Commons, with a timecoded summary of the conversation.
>
> Sincerely,
>
> Liam
>
>
> On Tue, 7 Feb 2023 at 23:29, Samuel Klein  wrote:
>
>> Chris - My thoughts exactly. A satisfying report: useful, informative,
>> densely linked.
>>
>> TLDR:  revenue at 2% of the WMF total; projected to be cashflow positive
>> this year.
>> 9 FTEs, up-to-date landing page
>> , even headshot
>> photos for a majority of the team.
>> (And a subtle reminder that we should consider doing something awesome
>> with a community-led merch store!)
>>
>> Liam - for the product update, I'm curious how hosting costs + usage have
>> changed over the year (and implications for what we learn to optimize)
>>
>> SJ
>>
>> On Tue, Feb 7, 2023 at 10:16 AM Chris Keating 
>> wrote:
>>
>>> Thanks Liam! That looks admirably clear and very thorough - would be
>>> great to see this level of detail and transparency in other aspects of the
>>> WMF's work
>>>
>>> Chris/ The Land
>>>
>>> On Tue, 7 Feb 2023, 14:35 Liam Wyatt,  wrote:
>>>
 Dear all,

 Following the initial announcement and project launch in 2021, and
 press release about first customers in 2022, the Wikimedia Enterprise team
 has today published the *first financial report* and a summary of a
 forthcoming *product update*.

 This has been published today on the Diff blog, here:

 https://diff.wikimedia.org/2023/02/07/wikimedia-enterprise-financial-report-product-update/
 [also available in German
 
 ]

 One of the principles
  of
 the Wikimedia Enterprise project has been “the publication of overall
 revenue and expenses, differentiated from those of the Wikimedia Foundation
 in general, at least annually”. We are therefore proud to present the
 inaugural edition of the Wikimedia Enterprise financial report – covering
 the calendar-year 2022, its first year of operations.

 The update also includes a description of some of the API features that
 have been under development. While the primary use-case is companies which
 consistently require very high-speed updates of very large amounts of
 Wikimedia content, it is important to note that there are several
 free-access methods.

 If you have written questions or comments about the update, please
 share them on the project’s talkpage
 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Liam Wyatt]

Hello Sam, thank you for the kind words.

And also thank you to Chris and Martin for yours.


With regards to the “optimizations” mentioned in the product update: usage
change over the course of 2022 wasn’t really the motivating factor here
(given it’s only been one year so we’re fully expecting fluctuations), It’s
more about trying to increase the system’s efficiency and limit areas where
things could break at scale - in preparation for future demand. There has
been some increase in costs over the 2022 calendar year, as shown in the
finance report’s bar-graph and associated paragraph, but that was primarily
due to staffing changes, not hosting costs.

Our initial system architecture focused heavily on Wikipedia database dumps
and now we’re focusing on expanding the “realtime” data feeds. We decided
to rebuild the architecture to look more like an event-based system, to
work alongside exported-data products, instead of adding on more services
on top of the dump generation.

As mentioned in the product update, for those interested in this topic
there are quarterly summaries of the technical work on the project’s
MediaWiki page: https://www.mediawiki.org/wiki/Wikimedia_Enterprise#Updates
But, if you’d like to talk through the implementation details and the
thinking behind it, then the best format is a real-time conversation. I
encourage you to come to the “office hours” public meeting this Friday -
etails at the top of the project page on Meta. Even if you can’t make it to
that, we’ll make sure to discuss the product update and I’ll be uploading
the recording afterwards to Commons, with a timecoded summary of the
conversation.

Sincerely,

Liam


On Tue, 7 Feb 2023 at 23:29, Samuel Klein  wrote:

> Chris - My thoughts exactly. A satisfying report: useful, informative,
> densely linked.
>
> TLDR:  revenue at 2% of the WMF total; projected to be cashflow positive
> this year.
> 9 FTEs, up-to-date landing page
> , even headshot
> photos for a majority of the team.
> (And a subtle reminder that we should consider doing something awesome
> with a community-led merch store!)
>
> Liam - for the product update, I'm curious how hosting costs + usage have
> changed over the year (and implications for what we learn to optimize)
>
> SJ
>
> On Tue, Feb 7, 2023 at 10:16 AM Chris Keating 
> wrote:
>
>> Thanks Liam! That looks admirably clear and very thorough - would be
>> great to see this level of detail and transparency in other aspects of the
>> WMF's work
>>
>> Chris/ The Land
>>
>> On Tue, 7 Feb 2023, 14:35 Liam Wyatt,  wrote:
>>
>>> Dear all,
>>>
>>> Following the initial announcement and project launch in 2021, and press
>>> release about first customers in 2022, the Wikimedia Enterprise team
>>> has today published the *first financial report* and a summary of a
>>> forthcoming *product update*.
>>>
>>> This has been published today on the Diff blog, here:
>>>
>>> https://diff.wikimedia.org/2023/02/07/wikimedia-enterprise-financial-report-product-update/
>>> [also available in German
>>> 
>>> ]
>>>
>>> One of the principles
>>>  of
>>> the Wikimedia Enterprise project has been “the publication of overall
>>> revenue and expenses, differentiated from those of the Wikimedia Foundation
>>> in general, at least annually”. We are therefore proud to present the
>>> inaugural edition of the Wikimedia Enterprise financial report – covering
>>> the calendar-year 2022, its first year of operations.
>>>
>>> The update also includes a description of some of the API features that
>>> have been under development. While the primary use-case is companies which
>>> consistently require very high-speed updates of very large amounts of
>>> Wikimedia content, it is important to note that there are several
>>> free-access methods.
>>>
>>> If you have written questions or comments about the update, please share
>>> them on the project’s talkpage
>>>  on Meta. As
>>> described in the blogpost, we consider this report covering the 2022
>>> calendar year to be a “beta” version. We are actively seeking feedback
>>> about how its structure, content, and explanations can be improved for the
>>> next edition in late 2023, which will cover the 2022-23 fiscal year.
>>>
>>>
>>> If you prefer real-time conversation: A public meeting will be hosted
>>> by the Enterprise team this Friday, February 10 @1900 UTC to discuss this
>>> announcement - details on the project homepage
>>> .
>>>
>>> If you have any other questions please consult the FAQ
>>> .
>>>
>>> Sincerely,
>>>
>>> * Liam Wyatt [Wittylama]*
>>>
>>> Senior Program Manager
>>> for *Enterprise,* *Campaigns, & 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Samuel Klein]

Chris - My thoughts exactly. A satisfying report: useful, informative,
densely linked.

TLDR:  revenue at 2% of the WMF total; projected to be cashflow positive
this year.
9 FTEs, up-to-date landing page
, even headshot
photos for a majority of the team.
(And a subtle reminder that we should consider doing something awesome with
a community-led merch store!)

Liam - for the product update, I'm curious how hosting costs + usage have
changed over the year (and implications for what we learn to optimize)

SJ

On Tue, Feb 7, 2023 at 10:16 AM Chris Keating 
wrote:

> Thanks Liam! That looks admirably clear and very thorough - would be great
> to see this level of detail and transparency in other aspects of the WMF's
> work
>
> Chris/ The Land
>
> On Tue, 7 Feb 2023, 14:35 Liam Wyatt,  wrote:
>
>> Dear all,
>>
>> Following the initial announcement and project launch in 2021, and press
>> release about first customers in 2022, the Wikimedia Enterprise team has
>> today published the *first financial report* and a summary of a
>> forthcoming *product update*.
>>
>> This has been published today on the Diff blog, here:
>>
>> https://diff.wikimedia.org/2023/02/07/wikimedia-enterprise-financial-report-product-update/
>> [also available in German
>> 
>> ]
>>
>> One of the principles
>>  of the 
>> Wikimedia
>> Enterprise project has been “the publication of overall revenue and
>> expenses, differentiated from those of the Wikimedia Foundation in general,
>> at least annually”. We are therefore proud to present the inaugural edition
>> of the Wikimedia Enterprise financial report – covering the calendar-year
>> 2022, its first year of operations.
>>
>> The update also includes a description of some of the API features that
>> have been under development. While the primary use-case is companies which
>> consistently require very high-speed updates of very large amounts of
>> Wikimedia content, it is important to note that there are several
>> free-access methods.
>>
>> If you have written questions or comments about the update, please share
>> them on the project’s talkpage
>>  on Meta. As
>> described in the blogpost, we consider this report covering the 2022
>> calendar year to be a “beta” version. We are actively seeking feedback
>> about how its structure, content, and explanations can be improved for the
>> next edition in late 2023, which will cover the 2022-23 fiscal year.
>>
>>
>> If you prefer real-time conversation: A public meeting will be hosted by
>> the Enterprise team this Friday, February 10 @1900 UTC to discuss this
>> announcement - details on the project homepage
>> .
>>
>> If you have any other questions please consult the FAQ
>> .
>>
>> Sincerely,
>>
>> * Liam Wyatt [Wittylama]*
>>
>> Senior Program Manager
>> for *Enterprise,* *Campaigns, & WikiCite*
>> Wikimedia Foundation
>>
>> ___
>> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
>> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>> https://meta.wikimedia.org/wiki/Wikimedia-l
>> Public archives at
>> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/DVYUXJMRGYUKRZI6VRUVW2JKPU27QDF3/
>> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MDW4LVJFKC2KVHTMMNMUN6ZV3FKRM6H7/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org



-- 
Samuel Klein  @metasj   w:user:sj  +1 617 529 4266
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/XW2DEBSZE5736AXUSEQEE37UL5FTWMRW/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[DerHexer via Wikimedia-l]

 Thanks too for the German translation of the very detailed and transparent 
report!
Best,DerHexer
Am Dienstag, 7. Februar 2023 um 16:16:31 MEZ hat Chris Keating 
 Folgendes geschrieben:  
 
 Thanks Liam! That looks admirably clear and very thorough - would be great to 
see this level of detail and transparency in other aspects of the WMF's work
Chris/ The Land
On Tue, 7 Feb 2023, 14:35 Liam Wyatt,  wrote:


Dear all,


Following the initial announcement and project launch in 2021, and press 
release about first customers in 2022, the Wikimedia Enterprise team has today 
published the first financial report and a summary of a forthcoming product 
update.


This has been published today on the Diff blog, here:
https://diff.wikimedia.org/2023/02/07/wikimedia-enterprise-financial-report-product-update/
[also available in German]

One of the principles of the Wikimedia Enterprise project has been “the 
publication of overall revenue and expenses, differentiated from those of the 
Wikimedia Foundation in general, at least annually”. We are therefore proud to 
present the inaugural edition of the Wikimedia Enterprise financial report – 
covering the calendar-year 2022, its first year of operations.


The update also includes a description of some of the API features that have 
been under development. While the primary use-case is companies which 
consistently require very high-speed updates of very large amounts of Wikimedia 
content, it is important to note that there are several free-access methods.

If you have written questions or comments about the update, please share them 
on the project’s talkpage on Meta. As described in the blogpost, we consider 
this report covering the 2022 calendar year to be a “beta” version. We are 
actively seeking feedback about how its structure, content, and explanations 
can be improved for the next edition in late 2023, which will cover the 2022-23 
fiscal year.


If you prefer real-time conversation: A public meeting will be hosted by the 
Enterprise team this Friday, February 10 @1900 UTC to discuss this announcement 
- details on the project homepage.

If you have any other questions please consult the FAQ.

Sincerely,

| 

 | 
 Liam Wyatt [Wittylama]

| 
Senior Program Manager 
for Enterprise, Campaigns, & WikiCite

Wikimedia Foundation |


 |

___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/DVYUXJMRGYUKRZI6VRUVW2JKPU27QDF3/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MDW4LVJFKC2KVHTMMNMUN6ZV3FKRM6H7/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org  ___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/PTLRHZVK4SSU7N46OLNZGIWQZE7K7DUX/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Chris Keating]

Thanks Liam! That looks admirably clear and very thorough - would be great
to see this level of detail and transparency in other aspects of the WMF's
work

Chris/ The Land

On Tue, 7 Feb 2023, 14:35 Liam Wyatt,  wrote:

> Dear all,
>
> Following the initial announcement and project launch in 2021, and press
> release about first customers in 2022, the Wikimedia Enterprise team has
> today published the *first financial report* and a summary of a
> forthcoming *product update*.
>
> This has been published today on the Diff blog, here:
>
> https://diff.wikimedia.org/2023/02/07/wikimedia-enterprise-financial-report-product-update/
> [also available in German
> 
> ]
>
> One of the principles
>  of the 
> Wikimedia
> Enterprise project has been “the publication of overall revenue and
> expenses, differentiated from those of the Wikimedia Foundation in general,
> at least annually”. We are therefore proud to present the inaugural edition
> of the Wikimedia Enterprise financial report – covering the calendar-year
> 2022, its first year of operations.
>
> The update also includes a description of some of the API features that
> have been under development. While the primary use-case is companies which
> consistently require very high-speed updates of very large amounts of
> Wikimedia content, it is important to note that there are several
> free-access methods.
>
> If you have written questions or comments about the update, please share
> them on the project’s talkpage
>  on Meta. As
> described in the blogpost, we consider this report covering the 2022
> calendar year to be a “beta” version. We are actively seeking feedback
> about how its structure, content, and explanations can be improved for the
> next edition in late 2023, which will cover the 2022-23 fiscal year.
>
>
> If you prefer real-time conversation: A public meeting will be hosted by
> the Enterprise team this Friday, February 10 @1900 UTC to discuss this
> announcement - details on the project homepage
> .
>
> If you have any other questions please consult the FAQ
> .
>
> Sincerely,
>
> * Liam Wyatt [Wittylama]*
>
> Senior Program Manager
> for *Enterprise,* *Campaigns, & WikiCite*
> Wikimedia Foundation
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/DVYUXJMRGYUKRZI6VRUVW2JKPU27QDF3/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MDW4LVJFKC2KVHTMMNMUN6ZV3FKRM6H7/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Liam Wyatt]

Dear all,

Following the initial announcement and project launch in 2021, and press
release about first customers in 2022, the Wikimedia Enterprise team has
today published the *first financial report* and a summary of a
forthcoming *product
update*.

This has been published today on the Diff blog, here:
https://diff.wikimedia.org/2023/02/07/wikimedia-enterprise-financial-report-product-update/
[also available in German

]

One of the principles
 of
the Wikimedia
Enterprise project has been “the publication of overall revenue and
expenses, differentiated from those of the Wikimedia Foundation in general,
at least annually”. We are therefore proud to present the inaugural edition
of the Wikimedia Enterprise financial report – covering the calendar-year
2022, its first year of operations.

The update also includes a description of some of the API features that
have been under development. While the primary use-case is companies which
consistently require very high-speed updates of very large amounts of
Wikimedia content, it is important to note that there are several
free-access methods.

If you have written questions or comments about the update, please share
them on the project’s talkpage
 on Meta. As
described in the blogpost, we consider this report covering the 2022
calendar year to be a “beta” version. We are actively seeking feedback
about how its structure, content, and explanations can be improved for the
next edition in late 2023, which will cover the 2022-23 fiscal year.


If you prefer real-time conversation: A public meeting will be hosted by
the Enterprise team this Friday, February 10 @1900 UTC to discuss this
announcement - details on the project homepage
.

If you have any other questions please consult the FAQ
.

Sincerely,

* Liam Wyatt [Wittylama]*

Senior Program Manager
for *Enterprise,* *Campaigns, & WikiCite*
Wikimedia Foundation
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/DVYUXJMRGYUKRZI6VRUVW2JKPU27QDF3/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Liam Wyatt]

Thank you SJ, I think you've said it better than I could.

As I hope everyone can appreciate - different audiences are interested in
different pieces of information and look for that information in different
places. Today's 'press release' is differently formatted to, and with
different focus from, the message I've sent here (and Meta). And those are
different again from the (also public) 'tuning session' quarterly update
slides. Equally, for example, technical roadmap updates about this project
are published on its MediaWiki page
https://www.mediawiki.org/wiki/Wikimedia_Enterprise and the code is on its
GitHub page https://github.com/wikimedia/OKAPI - both of which have also
received substantial updates recently that I did not mention in my earlier
email because they were less relevant to this audience. But, since we're
talking about the different interests of different audiences I'm happy to
link them here now too.

For the benefit of the wider community here, it should be noted that I've
replied to Andres' comments about these quarterly update slides, with
relation to the Enterprise project, when he first raised them the 15th of
June on the Meta talkpage
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Enterprise#How_are_we_doing?
and also on the WikipediaWeekly facebook group the same day
https://www.facebook.com/groups/wikipediaweekly/permalink/5144372348943888/
.

Sincerely,
- Liam
Peace, Love & Metadata.


On Tue, 21 Jun 2022 at 22:40, Samuel Klein  wrote:

> Andreas,
>
> Relax.
>
> There are three slides in that deck about Enterprise, much less detailed
> than the summary Liam just shared.
> There is no contradiction involved, and the transparency of sharing
> quarterly slides is all I could imagine wanting.
> In its context, they focus on OKRs and specific metrics, which are less
> relevant to this conversation (and were arbitrary in the first place).
>
> If you constantly cry wolf, valid concerns will not be heard.
> Meanwhile you are making this list less pleasant and less useful for
> normal, undramatic discussion.
>
> SJ
>
> On Tue, Jun 21, 2022 at 3:55 PM Andreas Kolbe  wrote:
>
>> Dear Liam,
>>
>> There seem to be (at least) two types of presentations on Wikimedia
>> Enterprise here: a PR-optimised one for public consumption, given here, and
>> an internal one. I'd like the difference between the two to be smaller,
>> ideally, and for the community (also) to be given the internal one, as
>> found in Advancement's Q3 "tuning session" (quarterly review):
>>
>>
>> https://commons.wikimedia.org/w/index.php?title=File:Wikimedia_Foundation_Tuning_Session_FY21-22_Q3_Advancement.pdf=7
>>
>> This says:
>>
>> --
>>
>> *The situation *
>> Although we successfully closed an initial set of paying customers for
>> Wikimedia Enterprise at the end of the last calendar year, and have
>> continued to have ongoing sales conversations with additional potential
>> customers, we have been unable to close additional customers as quickly as
>> we projected due to unanticipated legal and product requirements, and will
>> not hit the revenue target for FY21/22.
>>
>> *The impact *
>> We are developing a clearer picture of what is required to successfully
>> scale sales of the Wikimedia Enterprise product within our non-profit
>> context. In particular, we need to redefine, and better articulate, the
>> relationship between our free and paid APIs, so that we can successfully
>> explain why they would choose our paid, commercial-grade services rather
>> than our free APIs.
>>
>> *Recommendation *
>> We are working with the legal team to develop a contractual structure
>> that allows us to sell to a wider set of countries, and with the product
>> team to better delineate the relationship between our free and paid API
>> services, so that by the end of this calendar year there will be a clear
>> value proposition that drives commercial customers to pay for the
>> Enterprise APIs.
>>
>> --
>>
>> Note that this tuning session presentation, too, is marked "PUBLIC", so
>> presumably there is a non-public version of that file as well.
>>
>> I find all of this (which I doubt is your decision, so please don't take
>> it as a criticism of you personally) lamentable. The community is the WMF's
>> partner in all of this. Why not speak openly to us? We are not paying
>> customers who need to be wooed, or wowed.
>>
>> And no – the solution is not to stop publishing the quarterly reviews, or
>> to delay their publication even more.
>>
>> Best,
>> Andreas
>>
>>
>>
>> On Tue, Jun 21, 2022 at 5:11 PM Liam Wyatt  wrote:
>>
>>> Dear all,
>>>
>>>
>>>
>>> TL;DR: Today the Wikimedia Foundation published a press release[1]
>>> about the “Wikimedia Enterprise” API project - announcing our first set
>>> of customers, as well as a new self-signup system. This is a significant
>>> milestone because it fulfills several promises we have made to ourselves
>>> and to the movement. There will be a community open meeting on Thursday
>>> 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Samuel Klein]

Andreas,

Relax.

There are three slides in that deck about Enterprise, much less detailed
than the summary Liam just shared.
There is no contradiction involved, and the transparency of sharing
quarterly slides is all I could imagine wanting.
In its context, they focus on OKRs and specific metrics, which are less
relevant to this conversation (and were arbitrary in the first place).

If you constantly cry wolf, valid concerns will not be heard.
Meanwhile you are making this list less pleasant and less useful for
normal, undramatic discussion.

SJ

On Tue, Jun 21, 2022 at 3:55 PM Andreas Kolbe  wrote:

> Dear Liam,
>
> There seem to be (at least) two types of presentations on Wikimedia
> Enterprise here: a PR-optimised one for public consumption, given here, and
> an internal one. I'd like the difference between the two to be smaller,
> ideally, and for the community (also) to be given the internal one, as
> found in Advancement's Q3 "tuning session" (quarterly review):
>
>
> https://commons.wikimedia.org/w/index.php?title=File:Wikimedia_Foundation_Tuning_Session_FY21-22_Q3_Advancement.pdf=7
>
> This says:
>
> --
>
> *The situation *
> Although we successfully closed an initial set of paying customers for
> Wikimedia Enterprise at the end of the last calendar year, and have
> continued to have ongoing sales conversations with additional potential
> customers, we have been unable to close additional customers as quickly as
> we projected due to unanticipated legal and product requirements, and will
> not hit the revenue target for FY21/22.
>
> *The impact *
> We are developing a clearer picture of what is required to successfully
> scale sales of the Wikimedia Enterprise product within our non-profit
> context. In particular, we need to redefine, and better articulate, the
> relationship between our free and paid APIs, so that we can successfully
> explain why they would choose our paid, commercial-grade services rather
> than our free APIs.
>
> *Recommendation *
> We are working with the legal team to develop a contractual structure that
> allows us to sell to a wider set of countries, and with the product team to
> better delineate the relationship between our free and paid API services,
> so that by the end of this calendar year there will be a clear value
> proposition that drives commercial customers to pay for the Enterprise APIs.
>
> --
>
> Note that this tuning session presentation, too, is marked "PUBLIC", so
> presumably there is a non-public version of that file as well.
>
> I find all of this (which I doubt is your decision, so please don't take
> it as a criticism of you personally) lamentable. The community is the WMF's
> partner in all of this. Why not speak openly to us? We are not paying
> customers who need to be wooed, or wowed.
>
> And no – the solution is not to stop publishing the quarterly reviews, or
> to delay their publication even more.
>
> Best,
> Andreas
>
>
>
> On Tue, Jun 21, 2022 at 5:11 PM Liam Wyatt  wrote:
>
>> Dear all,
>>
>>
>>
>> TL;DR: Today the Wikimedia Foundation published a press release[1] about
>> the “Wikimedia Enterprise” API project - announcing our first set of
>> customers, as well as a new self-signup system. This is a significant
>> milestone because it fulfills several promises we have made to ourselves
>> and to the movement. There will be a community open meeting on Thursday
>> 23 June @ 1700 UTC as documented on our Meta page.[2] The text of this
>> email is also published on the talkpage - please centralise any
>> comments/feedback there.[3]
>>
>> Details
>>
>> I am writing today with details of the latest developments in the
>> “Wikimedia Enterprise” API project. This follows the project’s
>> community-discussion phase, which began approximately one year ago, focused
>> on Meta [and also this wikimedia-l thread]. Then, this past October, we
>> issued a press release announcing that we were “open for business” on the
>> project’s new site.[4] This wikimedia-l email thread contains the details
>> of those previous phases.
>>
>> Now is the third and final major announcement in this journey from “idea”
>> to “reality”. Today’s press release,[1] and associated story on the
>> project’s new “news” page,[5] states that:
>>
>>-
>>
>>Two well known organisations will be announced as the first customers
>>of the project. One is a major social/search corporation [Google], as
>>our first official paying customer. This also means that the project is 
>> now
>>covering its current operating costs. The other is a movement partner and
>>nonprofit organization [The Internet Archive] that will receive access at
>>no cost.
>>-
>>
>>Anyone will be able to sign up for an account and use/access the
>>service [but not at a commercial scale] for free. Furthermore,
>>payments for usage above that threshold will be calculated simply and
>>publicly based on the number of API requests and gigabytes of data used.
>> 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Andreas Kolbe]

Dear Liam,

There seem to be (at least) two types of presentations on Wikimedia
Enterprise here: a PR-optimised one for public consumption, given here, and
an internal one. I'd like the difference between the two to be smaller,
ideally, and for the community (also) to be given the internal one, as
found in Advancement's Q3 "tuning session" (quarterly review):

https://commons.wikimedia.org/w/index.php?title=File:Wikimedia_Foundation_Tuning_Session_FY21-22_Q3_Advancement.pdf=7

This says:

--

*The situation *
Although we successfully closed an initial set of paying customers for
Wikimedia Enterprise at the end of the last calendar year, and have
continued to have ongoing sales conversations with additional potential
customers, we have been unable to close additional customers as quickly as
we projected due to unanticipated legal and product requirements, and will
not hit the revenue target for FY21/22.

*The impact *
We are developing a clearer picture of what is required to successfully
scale sales of the Wikimedia Enterprise product within our non-profit
context. In particular, we need to redefine, and better articulate, the
relationship between our free and paid APIs, so that we can successfully
explain why they would choose our paid, commercial-grade services rather
than our free APIs.

*Recommendation *
We are working with the legal team to develop a contractual structure that
allows us to sell to a wider set of countries, and with the product team to
better delineate the relationship between our free and paid API services,
so that by the end of this calendar year there will be a clear value
proposition that drives commercial customers to pay for the Enterprise APIs.

--

Note that this tuning session presentation, too, is marked "PUBLIC", so
presumably there is a non-public version of that file as well.

I find all of this (which I doubt is your decision, so please don't take it
as a criticism of you personally) lamentable. The community is the WMF's
partner in all of this. Why not speak openly to us? We are not paying
customers who need to be wooed, or wowed.

And no – the solution is not to stop publishing the quarterly reviews, or
to delay their publication even more.

Best,
Andreas



On Tue, Jun 21, 2022 at 5:11 PM Liam Wyatt  wrote:

> Dear all,
>
>
>
> TL;DR: Today the Wikimedia Foundation published a press release[1] about
> the “Wikimedia Enterprise” API project - announcing our first set of
> customers, as well as a new self-signup system. This is a significant
> milestone because it fulfills several promises we have made to ourselves
> and to the movement. There will be a community open meeting on Thursday
> 23 June @ 1700 UTC as documented on our Meta page.[2] The text of this
> email is also published on the talkpage - please centralise any
> comments/feedback there.[3]
>
> Details
>
> I am writing today with details of the latest developments in the
> “Wikimedia Enterprise” API project. This follows the project’s
> community-discussion phase, which began approximately one year ago, focused
> on Meta [and also this wikimedia-l thread]. Then, this past October, we
> issued a press release announcing that we were “open for business” on the
> project’s new site.[4] This wikimedia-l email thread contains the details
> of those previous phases.
>
> Now is the third and final major announcement in this journey from “idea”
> to “reality”. Today’s press release,[1] and associated story on the
> project’s new “news” page,[5] states that:
>
>-
>
>Two well known organisations will be announced as the first customers
>of the project. One is a major social/search corporation [Google], as
>our first official paying customer. This also means that the project is now
>covering its current operating costs. The other is a movement partner and
>nonprofit organization [The Internet Archive] that will receive access at
>no cost.
>-
>
>Anyone will be able to sign up for an account and use/access the
>service [but not at a commercial scale] for free. Furthermore,
>payments for usage above that threshold will be calculated simply and
>publicly based on the number of API requests and gigabytes of data used.
>(Other free access methods for the dataset continue to exist, as documented
>on our Meta FAQ)[6]
>-
>
>The API’s metadata has been expanded to include the beta version of
>what we are calling “credibility signals”. This is already public
>information (such as pageviews, edit-rates, and page-protection status
>changes) packaged within the single data feed to help users make more
>informed decisions about when they should refresh their copy of the
>dataset. (Emphasis on ‘beta’, as this is not available on all versions of
>the product yet.)
>
>
> This announcement is a significant milestone because it fulfills several
> promises we have made to ourselves and to the movement, namely that:
>
>-
>
>We 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Liam Wyatt]

Thank you SJ!
To your questions in order:
1) This is all metadata that is already publicly available (e.g. ORES,
page-protection status change, high % pageviews changes...). Crucially - it
is not creating some "value judgement" about an article or particular edit
but taking the information that Wikimedians (and therefore readers)
*already have access to* and helping API users make informed choices about
how to use the data. If the service proves effective, useful, and there's
community interest - anything's possible - but I will re-emphasise though
that this is in beta and how we grow/improve/incorporate this concept is
still in flux. General technical documentation at our MediaWiki page
https://www.mediawiki.org/wiki/Wikimedia_Enterprise API documentation on
the project's website: https://enterprise.wikimedia.com/docs/

2) Indeed, we have already met with the DBpedia team. We've been,
unsurprisingly, focused on launching v1.0 but we can and will now return to
some of those conversations.

- Liam Wyatt

On Tue, 21 Jun 2022 at 18:47, Samuel Klein  wrote:

> Beautiful work.
> ~ Are there plans to make the credibility signals visible somehow (in
> sparklines? in the header?) to readers who visit articles?
> ~ As you add wikidata, please consider also working with dbpedia (which
> has expanded its range of source material) to see how we can make their
> integration flows easier.
>
> On Tue, Jun 21, 2022 at 12:12 PM Liam Wyatt  wrote:
>
>> Dear all,
>>
>>
>>
>> TL;DR: Today the Wikimedia Foundation published a press release[1] about
>> the “Wikimedia Enterprise” API project - announcing our first set of
>> customers, as well as a new self-signup system. This is a significant
>> milestone because it fulfills several promises we have made to ourselves
>> and to the movement. There will be a community open meeting on Thursday
>> 23 June @ 1700 UTC as documented on our Meta page.[2] The text of this
>> email is also published on the talkpage - please centralise any
>> comments/feedback there.[3]
>>
>> Details
>>
>> I am writing today with details of the latest developments in the
>> “Wikimedia Enterprise” API project. This follows the project’s
>> community-discussion phase, which began approximately one year ago, focused
>> on Meta [and also this wikimedia-l thread]. Then, this past October, we
>> issued a press release announcing that we were “open for business” on the
>> project’s new site.[4] This wikimedia-l email thread contains the details
>> of those previous phases.
>>
>> Now is the third and final major announcement in this journey from “idea”
>> to “reality”. Today’s press release,[1] and associated story on the
>> project’s new “news” page,[5] states that:
>>
>>-
>>
>>Two well known organisations will be announced as the first customers
>>of the project. One is a major social/search corporation [Google], as
>>our first official paying customer. This also means that the project is 
>> now
>>covering its current operating costs. The other is a movement partner and
>>nonprofit organization [The Internet Archive] that will receive access at
>>no cost.
>>-
>>
>>Anyone will be able to sign up for an account and use/access the
>>service [but not at a commercial scale] for free. Furthermore,
>>payments for usage above that threshold will be calculated simply and
>>publicly based on the number of API requests and gigabytes of data used.
>>(Other free access methods for the dataset continue to exist, as 
>> documented
>>on our Meta FAQ)[6]
>>-
>>
>>The API’s metadata has been expanded to include the beta version of
>>what we are calling “credibility signals”. This is already public
>>information (such as pageviews, edit-rates, and page-protection status
>>changes) packaged within the single data feed to help users make more
>>informed decisions about when they should refresh their copy of the
>>dataset. (Emphasis on ‘beta’, as this is not available on all versions of
>>the product yet.)
>>
>>
>> This announcement is a significant milestone because it fulfills several
>> promises we have made to ourselves and to the movement, namely that:
>>
>>-
>>
>>We have built something that commercial organisations who are already
>>heavy users of Wikimedia content and Wikimedia Foundation services are
>>willing to invest in. The pricing is based on estimated usage, resulting 
>> in
>>a more manageable and transparent cost structure. The project is now
>>covering its current operating expenses. In addition, we requested and
>>received a public affirmation/support letter from the Board for the
>>project’s financial operating principles, ensuring that commercial revenue
>>will only ever be a minority of the total and their oversight for any
>>future high value contracts.[7]
>>-
>>
>>The nonprofit partner will receive access at no cost, demonstrating a
>>first practical example of how this 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Samuel Klein]

Beautiful work.
~ Are there plans to make the credibility signals visible somehow (in
sparklines? in the header?) to readers who visit articles?
~ As you add wikidata, please consider also working with dbpedia (which has
expanded its range of source material) to see how we can make their
integration flows easier.

On Tue, Jun 21, 2022 at 12:12 PM Liam Wyatt  wrote:

> Dear all,
>
>
>
> TL;DR: Today the Wikimedia Foundation published a press release[1] about
> the “Wikimedia Enterprise” API project - announcing our first set of
> customers, as well as a new self-signup system. This is a significant
> milestone because it fulfills several promises we have made to ourselves
> and to the movement. There will be a community open meeting on Thursday
> 23 June @ 1700 UTC as documented on our Meta page.[2] The text of this
> email is also published on the talkpage - please centralise any
> comments/feedback there.[3]
>
> Details
>
> I am writing today with details of the latest developments in the
> “Wikimedia Enterprise” API project. This follows the project’s
> community-discussion phase, which began approximately one year ago, focused
> on Meta [and also this wikimedia-l thread]. Then, this past October, we
> issued a press release announcing that we were “open for business” on the
> project’s new site.[4] This wikimedia-l email thread contains the details
> of those previous phases.
>
> Now is the third and final major announcement in this journey from “idea”
> to “reality”. Today’s press release,[1] and associated story on the
> project’s new “news” page,[5] states that:
>
>-
>
>Two well known organisations will be announced as the first customers
>of the project. One is a major social/search corporation [Google], as
>our first official paying customer. This also means that the project is now
>covering its current operating costs. The other is a movement partner and
>nonprofit organization [The Internet Archive] that will receive access at
>no cost.
>-
>
>Anyone will be able to sign up for an account and use/access the
>service [but not at a commercial scale] for free. Furthermore,
>payments for usage above that threshold will be calculated simply and
>publicly based on the number of API requests and gigabytes of data used.
>(Other free access methods for the dataset continue to exist, as documented
>on our Meta FAQ)[6]
>-
>
>The API’s metadata has been expanded to include the beta version of
>what we are calling “credibility signals”. This is already public
>information (such as pageviews, edit-rates, and page-protection status
>changes) packaged within the single data feed to help users make more
>informed decisions about when they should refresh their copy of the
>dataset. (Emphasis on ‘beta’, as this is not available on all versions of
>the product yet.)
>
>
> This announcement is a significant milestone because it fulfills several
> promises we have made to ourselves and to the movement, namely that:
>
>-
>
>We have built something that commercial organisations who are already
>heavy users of Wikimedia content and Wikimedia Foundation services are
>willing to invest in. The pricing is based on estimated usage, resulting in
>a more manageable and transparent cost structure. The project is now
>covering its current operating expenses. In addition, we requested and
>received a public affirmation/support letter from the Board for the
>project’s financial operating principles, ensuring that commercial revenue
>will only ever be a minority of the total and their oversight for any
>future high value contracts.[7]
>-
>
>The nonprofit partner will receive access at no cost, demonstrating a
>first practical example of how this project supports the mission of
>knowledge access while also providing a new revenue stream.
>-
>
>The ‘trial’ tier of the service is primarily designed to allow
>potential customers to determine whether they want to use it in commercial
>production environments, but it also allows anyone to see what is ‘in’
>the API. Moreover, it will allow volunteers or researchers to access the
>service for free at a non-commercial scale. If those people have a
>mission-relevant use-case that requires them to continue to use the 
> Enterprise
>API above that scale (i.e. that isn’t viable using other APIs/dumps),
>we will continue to provide them with free access.
>-
>
>The ‘credibility signals’ concept means that vandalism and errors
>should appear less often and/or be removed more quickly in downstream
>services such as search engines. [Note, how and when customers incorporate
>features is their own decision].
>
>
> While we are proud to announce these customers, it is important to note
> that our market research has identified a significant gap in our
> movement’s ability to have Wikimedia knowledge used. 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Liam Wyatt]

Dear all,



TL;DR: Today the Wikimedia Foundation published a press release[1] about
the “Wikimedia Enterprise” API project - announcing our first set of
customers, as well as a new self-signup system. This is a significant
milestone because it fulfills several promises we have made to ourselves
and to the movement. There will be a community open meeting on Thursday 23
June @ 1700 UTC as documented on our Meta page.[2] The text of this email
is also published on the talkpage - please centralise any comments/feedback
there.[3]

Details

I am writing today with details of the latest developments in the
“Wikimedia Enterprise” API project. This follows the project’s
community-discussion phase, which began approximately one year ago, focused
on Meta [and also this wikimedia-l thread]. Then, this past October, we
issued a press release announcing that we were “open for business” on the
project’s new site.[4] This wikimedia-l email thread contains the details
of those previous phases.

Now is the third and final major announcement in this journey from “idea”
to “reality”. Today’s press release,[1] and associated story on the
project’s new “news” page,[5] states that:

   -

   Two well known organisations will be announced as the first customers of
   the project. One is a major social/search corporation [Google], as our
   first official paying customer. This also means that the project is now
   covering its current operating costs. The other is a movement partner and
   nonprofit organization [The Internet Archive] that will receive access at
   no cost.
   -

   Anyone will be able to sign up for an account and use/access the service
   [but not at a commercial scale] for free. Furthermore, payments for
   usage above that threshold will be calculated simply and publicly based on
   the number of API requests and gigabytes of data used. (Other free access
   methods for the dataset continue to exist, as documented on our Meta FAQ)[6]
   -

   The API’s metadata has been expanded to include the beta version of what
   we are calling “credibility signals”. This is already public information
   (such as pageviews, edit-rates, and page-protection status changes)
   packaged within the single data feed to help users make more informed
   decisions about when they should refresh their copy of the dataset.
   (Emphasis on ‘beta’, as this is not available on all versions of the
   product yet.)


This announcement is a significant milestone because it fulfills several
promises we have made to ourselves and to the movement, namely that:

   -

   We have built something that commercial organisations who are already
   heavy users of Wikimedia content and Wikimedia Foundation services are
   willing to invest in. The pricing is based on estimated usage, resulting in
   a more manageable and transparent cost structure. The project is now
   covering its current operating expenses. In addition, we requested and
   received a public affirmation/support letter from the Board for the
   project’s financial operating principles, ensuring that commercial revenue
   will only ever be a minority of the total and their oversight for any
   future high value contracts.[7]
   -

   The nonprofit partner will receive access at no cost, demonstrating a
   first practical example of how this project supports the mission of
   knowledge access while also providing a new revenue stream.
   -

   The ‘trial’ tier of the service is primarily designed to allow potential
   customers to determine whether they want to use it in commercial production
   environments, but it also allows anyone to see what is ‘in’ the API.
   Moreover, it will allow volunteers or researchers to access the service for
   free at a non-commercial scale. If those people have a mission-relevant
   use-case that requires them to continue to use the Enterprise API above
   that scale (i.e. that isn’t viable using other APIs/dumps), we will
   continue to provide them with free access.
   -

   The ‘credibility signals’ concept means that vandalism and errors should
   appear less often and/or be removed more quickly in downstream services
   such as search engines. [Note, how and when customers incorporate features
   is their own decision].


While we are proud to announce these customers, it is important to note
that our market research has identified a significant gap in our movement’s
ability to have Wikimedia knowledge used. The world’s largest companies are
already using Wikimedia; we’re just providing a better way for them to do
so. But for everyone else, it is often too hard and they do not have the
resources (financial, technical, and human) to incorporate Wikimedia
information – even though they want to. In short: simply providing
legally-reusable knowledge is insufficient to enable reuse for a very large
portion of society.



And so, we are focusing a lot of our future product development on
this Knowledge
as a Service model - consistent with the 

[Wikimedia-l] Re: The Wikimedia Enterprise API project

[Liam Wyatt]

Dear all, A lot has happened since March when we Introduced the Wikimedia
Enterprise API

and began community conversations about the project’s development. Now is
an important milestone to give everyone:
1) an update responding to community advice we’ve received;  and
2) to describe what is happening next.


The idea of an API for the specific needs of the commercial sector had been
discussed for more than a decade

(both for the purposes of improving user experience, and also to diversify
revenue). The announcement in March introducing the Wikimedia Enterprise
API generated a lot of Wikimedia-community and mainstream-media attention -
most notably in WIRED
.
Since then, the team has been hard at work building the actual product and
hosting many conversations (regular public meetings and participation in
events including SWAN, Wikimania, EMWCon, Clinic) - as well as a
considerable volume of discussions on our meta talkpage
.
All of this has generated lots of suggestions, which we have endeavoured to
incorporate and respond to before the actual commercial launch. On behalf
of the whole team, I thank the many many people who have been willing and
able to share constructive feedback with us over these months. Links to
recordings from those meetings/presentations can be found on our meta
homepage:

https://meta.wikimedia.org/wiki/Wikimedia_Enterprise


1. To that end, here are some updates in response to community advice:


WMF Board statement.

Subsequent to the most recent WMF Board of Trustees meeting, a statement
reaffirming their support of the project, and in particular its operating
principles relating to its future revenue, has been published. You can find the
board Statement here
,
and the Enterprise operating principles on Meta here
.
Consistent community feedback was that our published principles were good
and sensible, but for such a new and unusual thing in our movement, an
overt statement from the Board of Trustees was requested. This statement
affirms that:

   - Revenues of the WMF obtained from commercial activities shall not
   surpass 30% of the total planned revenue via all sources (including
   donations) in that fiscal year, and no further revenue would be sought
   beyond that limit;
   - The Board of Trustees will be notified in advance of any large
   commercial agreements, giving them time for review - exactly mirroring the
   procedure for large gifts;
   - Revenue obtained from Wikimedia Enterprise services is under the
   oversight and control of procedures for revenue raised by the Wikimedia
   Foundation and the revenue will not be earmarked for a specific program.

Each of these things were already noted on-wiki, but they were very much
worthwhile re-stating formally. Equally it bears repeating: the existing
APIs and methods of accessing Wikimedia sites remain. The creation of this
optional commercial service, designed for those with specific high
data-volume demands, does not change the experience (legally or
technically) for anyone else.
Relatedy, and also in response to community suggestions, the formal
contracts which define the legal relationship of the non-profit Wikimedia
Foundation to this commercial activity, have now been published on the
governance wiki and linked from the related section on the project’s

FAQ
.


Free technical access for the community.

You will soon be able to access a copy of the Enterprise dataset, refreshed
each fortnight, at the Wikimedia dumps portal .
Furthermore a ‘daily dump + hourly diff’ version is also already available, via
Wikimedia Cloud Services
 to
any users of Toolforge, Cloud VPS, or PAWS. Both of these are provided to
anyone, for free (in both ‘gratis’ and ‘libre’ senses of the word).
Importantly, and consistent with community feedback, neither of these
access methods require any special request process to access them, other
than the existing terms of service on those platforms.

Software development updates are published monthly on our page on MediaWiki
 (as is the API
documentation