Hi Bodhisattwa,
See below.
On Fri, Oct 15, 2021 at 1:41 PM Bodhisattwa Mandal
<bodhisattwa.rgkmc(a)gmail.com> wrote:
>
> Also, is there any way to add info on existing tools?
I learned from Bryan yesterday that this is possible via toolsadmin
(Bryan helped with one of our tools yesterday via
https://toolsadmin.wikimedia.org/tools/id/wikinav for that particular
tool). Toolhub then updates the list of tools every hour and you
should see your tool in toolhub. I hope this helps.
And congratulations to all of you who have been involved in making
this launch and product happen. :)
Leila
>
> Regards,
> Bodhisattwa
>
> On Fri, 15 Oct 2021 at 19:53, Birgit Müller <bmueller(a)wikimedia.org> wrote:
>>
>> Thanks Galder :-) - answers are below:
>>
>> On Thu, Oct 14, 2021 at 9:38 PM Galder Gonzalez Larrañaga <galder158(a)hotmail.com> wrote:
>>>
>>> Thanks, Brigit, for this hub, it is great to have it! I have tried and can't find any way to look for tools that are not nominated as "Coolest Tool Award" besides looking for name. Is there a way for searching by categories?
>>
>>
>> Today you can try searching for various keywords to find tools in the catalog (i.e. "Wikidata", "image", "editor", "template" ...). We're interested in adding support for the community to organize tools in categories/based on use cases in the future. There are some notes from past Design Research on that in the Data Model documentation. [0]
>>
>> Please feel welcome to comment on the talk page if you have further questions or ideas! [1]
>>
>> Birgit
>>
>> [0] https://meta.wikimedia.org/wiki/Toolhub/Data_model#Tool_use_cases
>> [1] https://meta.wikimedia.org/wiki/Talk:Toolhub
>>
>>
>>>
>>>
>>> Thanks
>>> Galder
>>> ________________________________
>>> From: Birgit Müller <bmueller(a)wikimedia.org>
>>> Sent: Thursday, October 14, 2021 4:58 PM
>>> To: wikitech-l <wikitech-l(a)lists.wikimedia.org>; wikimedia-l(a)lists.wikimedia.org <wikimedia-l(a)lists.wikimedia.org>; Wikimedia Cloud Services general discussion and support <cloud(a)lists.wikimedia.org>; wikidata(a)lists.wikimedia.org <wikidata(a)lists.wikimedia.org>; wikitech-ambassadors(a)lists.wikimedia.org <wikitech-ambassadors(a)lists.wikimedia.org>
>>> Subject: [Wikimedia-l] Toolhub 1.0 is launched! Discover software tools used at Wikimedia
>>>
>>>
>>> Hi All,
>>>
>>> We are happy to announce the launch of Toolhub – a community-authored catalogue that aims to make software tools used in the Wikimedia movement discoverable to everyone.
>>>
>>>
>>> Community developed tools – including web applications, bots, gadgets, user scripts, lua modules, and more – play a significant role in the Wikimedia projects. These software applications address a wide range of use cases including finding bad faith edits and other content curation, bulk editing, collecting statistical information, creating special citations, and much more. About ⅓ of all edits are made by bots and tools. In addition, semi-automated edits are helped by user scripts, gadgets, and other editing assistance tools that run from the user's local computer or directly inside the wikis. There are thousands of tools available, but how can you find them?
>>>
>>>
>>> With Toolhub, you can document and find tools, promote their use in your wiki community, and help improve them by contributing data. You can create and share lists of tools relevant to your work - for example, for GLAM tools, or for wiki projects such as Women in Red.
>>>
>>>
>>> This first release provides a core set of functionalities, and contains an initial data set of about 1500 tools. Most of the initial tools in the catalog are imported from the same data files developers have created for Hay's Directory which has been a major inspiration for Toolhub.
>>>
>>>
>>> Toolhub serves developers and users of tools alike. It is part of our efforts to improve the infrastructure and services for technical contributors, captured under one of Technology’s top level objectives in the FY 2020-2021 and 2021-2022 annual plans: Tech Community Building. We hope to continue conversations with developers and users of tools, plan to improve Toolhub, and to further expand the functionality.
>>>
>>>
>>> A collaborative system and open developer platform
>>>
>>> Toolhub is built as an API driven platform that makes it possible to extend and remix the catalogue, and to make collecting and reusing information about tools as open and collaborative as we can. Everything that can be done interactively with the Toolhub website can also be done remotely through the API. We would love to hear from technical contributors interested in using the Toolhub API to build new tools that make new ways to add or consume information from Toolhub's catalog.
>>>
>>>
>>> Our decision record and weekly progress reports on Meta provide more insights in technical implementation details and decisions made throughout the development process. The Toolhub/About page provides information on project origin, research, use cases, data model, and roadmap. This recording from a lightning talk at ‘21 Wikimania gives an overview of the main aspects in 10 minutes.
>>>
>>>
>>> Thank you <3
>>>
>>> This project wouldn’t have been possible without the support, knowledge, ideas and prior work of many. One of the nicest side-effects of a release is that it’s a great opportunity to thank folks for their time and contributions :-)
>>>
>>>
>>> Husky, whose Hay's Directory provided the foundation for the data model used by Toolhub and inspired some of its features.
>>>
>>> Harej, for his invaluable contributions in the early stages of the Toolhub project.
>>>
>>> Our 'advisory board' - Giuseppe (SRE), Risker (editor, admin), Reedy (Security), Keegan (Community Relations), and Eran (volunteer developer & RTL expert) for providing their perspectives on key questions throughout the development process.
>>>
>>> Giuseppe, Kunal, Manuel, Effie, Cole and Emanuele from SRE and Majavah for their help on finding and resolving deployment issues.
>>>
>>> Dan and Jeena from Release Engineering for help with build tooling.
>>>
>>> Guillaume and the rest of the Search Platform team for supporting our search index needs.
>>>
>>> Manuel for supporting our database needs.
>>>
>>> Niklas and the whole translatewiki.net community for help with localization and internationalization.
>>>
>>> Rita, Olga, Alex, and Matthew from the Product Design team for their feedback on the Toolhub user interface.
>>>
>>> Scott from the Security team for our security readiness review.
>>>
>>> Amire, Kunal, Eran, Reedy, and Dan for contributing code to the project.
>>>
>>> Ricordisamoa, Quim, and the people participating in conversations on wikitech-l for T115650 which inspired this whole project.
>>>
>>> Finally, a huge thanks to all the folks who gave input and feedback on the talk page, in Phabricator, and at sessions - this is really appreciated!
>>>
>>>
>>> We hope that this new resource will be fun to explore, inspire you with new ideas, and ultimately be useful for your work.
>>>
>>>
>>> Feedback, bug reports, ideas and questions are more than welcome on the talk page of the project, or in Phabricator. Bryan (tech lead) & Seve (our new Product Manager) will be there to chat with interested folks and help with any questions. We are looking forward to evolving this project step-by-step and jointly with everyone!
>>>
>>>
>>> Birgit – on behalf of Technical Engagement & our Toolhub project team
>>>
>>>
>>>
>>> --
>>> Birgit Müller (she/her)
>>> Director of Technical Engagement
>>>
>>> Wikimedia Foundation
>>> _______________________________________________
>>> Wikimedia-l mailing list -- wikimedia-l(a)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…
>>> To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org
>>
>>
>>
>> --
>> Birgit Müller (she/her)
>> Director of Technical Engagement
>>
>> Wikimedia Foundation
>> _______________________________________________
>> Wikidata mailing list -- wikidata(a)lists.wikimedia.org
>> To unsubscribe send an email to wikidata-leave(a)lists.wikimedia.org
>
> _______________________________________________
> Wikidata mailing list -- wikidata(a)lists.wikimedia.org
> To unsubscribe send an email to wikidata-leave(a)lists.wikimedia.org
Thanks Galder :-) - answers are below:
On Thu, Oct 14, 2021 at 9:38 PM Galder Gonzalez Larrañaga <
galder158(a)hotmail.com> wrote:
> Thanks, Brigit, for this hub, it is great to have it! I have tried and
> can't find any way to look for tools that are not nominated as "Coolest
> Tool Award" besides looking for name. Is there a way for searching by
> categories?
>
Today you can try searching for various keywords to find tools in the
catalog (i.e. "Wikidata", "image", "editor", "template" ...). We're
interested in adding support for the community to organize tools in
categories/based on use cases in the future. There are some notes from past
Design Research on that in the Data Model documentation. [0]
Please feel welcome to comment on the talk page if you have further
questions or ideas! [1]
Birgit
[0] https://meta.wikimedia.org/wiki/Toolhub/Data_model#Tool_use_cases
[1] https://meta.wikimedia.org/wiki/Talk:Toolhub
>
> Thanks
> Galder
> ------------------------------
> *From:* Birgit Müller <bmueller(a)wikimedia.org>
> *Sent:* Thursday, October 14, 2021 4:58 PM
> *To:* wikitech-l <wikitech-l(a)lists.wikimedia.org>;
> wikimedia-l(a)lists.wikimedia.org <wikimedia-l(a)lists.wikimedia.org>;
> Wikimedia Cloud Services general discussion and support <
> cloud(a)lists.wikimedia.org>; wikidata(a)lists.wikimedia.org <
> wikidata(a)lists.wikimedia.org>; wikitech-ambassadors(a)lists.wikimedia.org <
> wikitech-ambassadors(a)lists.wikimedia.org>
> *Subject:* [Wikimedia-l] Toolhub 1.0 is launched! Discover software tools
> used at Wikimedia
>
>
> Hi All,
>
> We are happy to announce the launch of Toolhub
> <https://toolhub.wikimedia.org/> – a community-authored catalogue that
> aims to make software tools
> <https://meta.wikimedia.org/wiki/Toolhub#What_is_a_%22tool%22?> used in
> the Wikimedia movement discoverable to everyone.
>
> Community developed tools – including web applications, bots, gadgets,
> user scripts, lua modules, and more – play a significant role in the
> Wikimedia projects. These software applications address a wide range of use
> cases including finding bad faith edits and other content curation, bulk
> editing, collecting statistical information, creating special citations,
> and much more. About ⅓ of all edits are made by bots and tools. In
> addition, semi-automated edits are helped by user scripts, gadgets, and
> other editing assistance tools that run from the user's local computer or
> directly inside the wikis. There are thousands of tools available, but how
> can you find them?
>
> With Toolhub, you can document and find tools
> <https://meta.wikimedia.org/wiki/Toolhub>, promote their use in your wiki
> community, and help improve them by contributing data. You can create and
> share lists of tools relevant to your work - for example, for GLAM tools,
> or for wiki projects such as Women in Red.
>
> This first release provides a core set of functionalities
> <https://meta.wikimedia.org/wiki/Toolhub/Roadmap>, and contains an
> initial data set of about 1500 tools. Most of the initial tools in the
> catalog are imported from the same data files developers have created for Hay's
> Directory <https://hay.toolforge.org/directory/> which has been a major
> inspiration for Toolhub.
>
> Toolhub serves developers and users of tools alike. It is part of our
> efforts to improve the infrastructure and services for technical
> contributors, captured under one of Technology’s top level objectives in
> the FY 2020-2021 and 2021-2022 annual plans: Tech Community Building
> <https://www.mediawiki.org/wiki/Wikimedia_Technology/Annual_Plans/ERF_OKR:_T…>.
> We hope to continue conversations with developers and users of tools, plan
> to improve Toolhub, and to further expand the functionality.
>
> A collaborative system and open developer platform
>
> Toolhub is built as an API driven platform that makes it possible to
> extend and remix the catalogue, and to make collecting and reusing
> information about tools as open and collaborative as we can. Everything
> that can be done interactively with the Toolhub website can also be done
> remotely through the API. We would love to hear from technical
> contributors interested in using the Toolhub API
> <https://meta.wikimedia.org/wiki/Talk:Toolhub#API-use> to build new tools
> that make new ways to add or consume information from Toolhub's catalog.
>
> Our decision record
> <https://meta.wikimedia.org/wiki/Toolhub/Decision_record> and weekly
> progress reports
> <https://meta.wikimedia.org/wiki/Toolhub/Progress_reports> on Meta
> provide more insights in technical implementation details and decisions
> made throughout the development process. The Toolhub/About page
> <https://meta.wikimedia.org/wiki/Toolhub/About> provides information on
> project origin, research, use cases, data model, and roadmap. This recording
> from a lightning talk at ‘21 Wikimania
> <https://www.youtube.com/watch?v=J2hNm7bKjDo> gives an overview of the
> main aspects in 10 minutes.
>
> Thank you <3
>
> This project wouldn’t have been possible without the support, knowledge,
> ideas and prior work of many. One of the nicest side-effects of a release
> is that it’s a great opportunity to thank folks for their time and
> contributions :-)
>
>
> -
>
> Husky <https://meta.wikimedia.org/wiki/User:Husky>, whose Hay's
> Directory <https://hay.toolforge.org/directory/> provided the
> foundation for the data model used by Toolhub and inspired some of its
> features.
> -
>
> Harej <https://meta.wikimedia.org/wiki/User:Harej>, for his invaluable
> contributions in the early stages of the Toolhub project.
> -
>
> Our 'advisory board' - Giuseppe
> <https://meta.wikimedia.org/wiki/User:GLavagetto_(WMF)> (SRE), Risker
> <https://meta.wikimedia.org/wiki/User:Risker> (editor, admin), Reedy
> <https://meta.wikimedia.org/wiki/User:Reedy_(WMF)> (Security), Keegan
> <https://meta.wikimedia.org/wiki/User:Keegan_(WMF)> (Community
> Relations), and Eran
> <https://meta.wikimedia.org/wiki/User:%D7%A2%D7%A8%D7%9F> (volunteer
> developer & RTL expert) for providing their perspectives on key questions
> throughout the development process.
> -
>
> Giuseppe, Kunal <https://meta.wikimedia.org/wiki/User:Legoktm>, Manuel
> <https://meta.wikimedia.org/wiki/User:MArostegui_(WMF)>, Effie
> <https://meta.wikimedia.org/wiki/User:EMouzeli_(WMF)>, Cole
> <https://meta.wikimedia.org/wiki/User:CWhite_(WMF)> and Emanuele
> <https://meta.wikimedia.org/wiki/User:ERocca_(WMF)> from SRE and
> Majavah <https://en.wikipedia.org/wiki/User:Majavah> for their help on
> finding and resolving deployment issues.
> -
>
> Dan <https://www.mediawiki.org/wiki/User:Dzduvall> and Jeena
> <https://www.mediawiki.org/wiki/User:JHuneidi_(WMF)> from Release
> Engineering for help with build tooling.
> -
>
> Guillaume <https://www.mediawiki.org/wiki/User:GLederrey_(WMF)> and
> the rest of the Search Platform team for supporting our search index needs.
> -
>
> Manuel for supporting our database needs.
> -
>
> Niklas <https://meta.wikimedia.org/wiki/User:Nlaxstrom-WMF> and the
> whole translatewiki.net community for help with localization and
> internationalization.
> -
>
> Rita <https://meta.wikimedia.org/wiki/User:RHo_(WMF)>, Olga
> <https://meta.wikimedia.org/wiki/User:OTichonova_(WMF)>, Alex
> <https://meta.wikimedia.org/wiki/User:AHollender_(WMF)>, and Matthew
> <https://meta.wikimedia.org/wiki/User:MWilliams_(WMF)> from the Product
> Design <https://www.mediawiki.org/wiki/Design> team for their feedback
> on the Toolhub user interface.
> -
>
> Scott <https://www.mediawiki.org/wiki/User:SBassett_(WMF)> from the
> Security team for our security readiness review.
> -
>
> Amire <https://en.wikipedia.org/wiki/User:Amire80>, Kunal, Eran,
> Reedy, and Dan for contributing code to the project.
> -
>
> Ricordisamoa <https://meta.wikimedia.org/wiki/User:Ricordisamoa>, Quim
> <https://meta.wikimedia.org/wiki/User:Qgil-WMF>, and the people
> participating in conversations on wikitech-l
> <https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>
> for T115650 <https://phabricator.wikimedia.org/T115650> which inspired
> this whole project.
> -
>
> Finally, a huge thanks to all the folks who gave input and feedback on
> the talk page, in Phabricator, and at sessions - this is really
> appreciated!
>
>
> We hope that this new resource will be fun to explore, inspire you with
> new ideas, and ultimately be useful for your work.
>
> Feedback, bug reports, ideas and questions are more than welcome on the talk
> page of the project <https://meta.wikimedia.org/wiki/Talk:Toolhub>, or in
> Phabricator <https://phabricator.wikimedia.org/project/board/3224/>. Bryan
> (tech lead) & Seve (our new Product Manager) will be there to chat with
> interested folks and help with any questions. We are looking forward to
> evolving this project step-by-step and jointly with everyone!
>
> Birgit – on behalf of Technical Engagement & our Toolhub project team
>
>
> --
> Birgit Müller (she/her)
> Director of Technical Engagement
>
> Wikimedia Foundation <https://wikimediafoundation.org/>
> _______________________________________________
> Wikimedia-l mailing list -- wikimedia-l(a)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…
> To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org
--
Birgit Müller (she/her)
Director of Technical Engagement
Wikimedia Foundation <https://wikimediafoundation.org/>
This is priceless. Thank you Hay for leading the way :) and thanks to ev e
ry one who made this happen.
On Thu, Oct 14, 2021 at 4:04 PM MusikAnimal <musikanimal(a)gmail.com> wrote:
> A long time coming! The interface looks amazing and seems very well
> thought out. It's nice to have an official, single go-to for all things
> tools, user scripts, gadgets, etc. Huge thanks and kudos to everyone
> involved!
>
> ~ MA
>
> On Thu, Oct 14, 2021 at 3:37 PM Galder Gonzalez Larrañaga <
> galder158(a)hotmail.com> wrote:
>
>> Thanks, Brigit, for this hub, it is great to have it! I have tried and
>> can't find any way to look for tools that are not nominated as "Coolest
>> Tool Award" besides looking for name. Is there a way for searching by
>> categories?
>>
>> Thanks
>> Galder
>> ------------------------------
>> *From:* Birgit Müller <bmueller(a)wikimedia.org>
>> *Sent:* Thursday, October 14, 2021 4:58 PM
>> *To:* wikitech-l <wikitech-l(a)lists.wikimedia.org>;
>> wikimedia-l(a)lists.wikimedia.org <wikimedia-l(a)lists.wikimedia.org>;
>> Wikimedia Cloud Services general discussion and support <
>> cloud(a)lists.wikimedia.org>; wikidata(a)lists.wikimedia.org <
>> wikidata(a)lists.wikimedia.org>; wikitech-ambassadors(a)lists.wikimedia.org <
>> wikitech-ambassadors(a)lists.wikimedia.org>
>> *Subject:* [Wikimedia-l] Toolhub 1.0 is launched! Discover software
>> tools used at Wikimedia
>>
>>
>> Hi All,
>>
>> We are happy to announce the launch of Toolhub
>> <https://toolhub.wikimedia.org/> – a community-authored catalogue that
>> aims to make software tools
>> <https://meta.wikimedia.org/wiki/Toolhub#What_is_a_%22tool%22?> used in
>> the Wikimedia movement discoverable to everyone.
>>
>> Community developed tools – including web applications, bots, gadgets,
>> user scripts, lua modules, and more – play a significant role in the
>> Wikimedia projects. These software applications address a wide range of use
>> cases including finding bad faith edits and other content curation, bulk
>> editing, collecting statistical information, creating special citations,
>> and much more. About ⅓ of all edits are made by bots and tools. In
>> addition, semi-automated edits are helped by user scripts, gadgets, and
>> other editing assistance tools that run from the user's local computer or
>> directly inside the wikis. There are thousands of tools available, but how
>> can you find them?
>>
>> With Toolhub, you can document and find tools
>> <https://meta.wikimedia.org/wiki/Toolhub>, promote their use in your
>> wiki community, and help improve them by contributing data. You can create
>> and share lists of tools relevant to your work - for example, for GLAM
>> tools, or for wiki projects such as Women in Red.
>>
>> This first release provides a core set of functionalities
>> <https://meta.wikimedia.org/wiki/Toolhub/Roadmap>, and contains an
>> initial data set of about 1500 tools. Most of the initial tools in the
>> catalog are imported from the same data files developers have created for Hay's
>> Directory <https://hay.toolforge.org/directory/> which has been a major
>> inspiration for Toolhub.
>>
>> Toolhub serves developers and users of tools alike. It is part of our
>> efforts to improve the infrastructure and services for technical
>> contributors, captured under one of Technology’s top level objectives in
>> the FY 2020-2021 and 2021-2022 annual plans: Tech Community Building
>> <https://www.mediawiki.org/wiki/Wikimedia_Technology/Annual_Plans/ERF_OKR:_T…>.
>> We hope to continue conversations with developers and users of tools,
>> plan to improve Toolhub, and to further expand the functionality.
>>
>> A collaborative system and open developer platform
>>
>> Toolhub is built as an API driven platform that makes it possible to
>> extend and remix the catalogue, and to make collecting and reusing
>> information about tools as open and collaborative as we can. Everything
>> that can be done interactively with the Toolhub website can also be done
>> remotely through the API. We would love to hear from technical
>> contributors interested in using the Toolhub API
>> <https://meta.wikimedia.org/wiki/Talk:Toolhub#API-use> to build new
>> tools that make new ways to add or consume information from Toolhub's
>> catalog.
>>
>> Our decision record
>> <https://meta.wikimedia.org/wiki/Toolhub/Decision_record> and weekly
>> progress reports
>> <https://meta.wikimedia.org/wiki/Toolhub/Progress_reports> on Meta
>> provide more insights in technical implementation details and decisions
>> made throughout the development process. The Toolhub/About page
>> <https://meta.wikimedia.org/wiki/Toolhub/About> provides information on
>> project origin, research, use cases, data model, and roadmap. This recording
>> from a lightning talk at ‘21 Wikimania
>> <https://www.youtube.com/watch?v=J2hNm7bKjDo> gives an overview of the
>> main aspects in 10 minutes.
>>
>> Thank you <3
>>
>> This project wouldn’t have been possible without the support, knowledge,
>> ideas and prior work of many. One of the nicest side-effects of a release
>> is that it’s a great opportunity to thank folks for their time and
>> contributions :-)
>>
>>
>> -
>>
>> Husky <https://meta.wikimedia.org/wiki/User:Husky>, whose Hay's
>> Directory <https://hay.toolforge.org/directory/> provided the
>> foundation for the data model used by Toolhub and inspired some of its
>> features.
>> -
>>
>> Harej <https://meta.wikimedia.org/wiki/User:Harej>, for his
>> invaluable contributions in the early stages of the Toolhub project.
>> -
>>
>> Our 'advisory board' - Giuseppe
>> <https://meta.wikimedia.org/wiki/User:GLavagetto_(WMF)> (SRE), Risker
>> <https://meta.wikimedia.org/wiki/User:Risker> (editor, admin), Reedy
>> <https://meta.wikimedia.org/wiki/User:Reedy_(WMF)> (Security), Keegan
>> <https://meta.wikimedia.org/wiki/User:Keegan_(WMF)> (Community
>> Relations), and Eran
>> <https://meta.wikimedia.org/wiki/User:%D7%A2%D7%A8%D7%9F> (volunteer
>> developer & RTL expert) for providing their perspectives on key questions
>> throughout the development process.
>> -
>>
>> Giuseppe, Kunal <https://meta.wikimedia.org/wiki/User:Legoktm>, Manuel
>> <https://meta.wikimedia.org/wiki/User:MArostegui_(WMF)>, Effie
>> <https://meta.wikimedia.org/wiki/User:EMouzeli_(WMF)>, Cole
>> <https://meta.wikimedia.org/wiki/User:CWhite_(WMF)> and Emanuele
>> <https://meta.wikimedia.org/wiki/User:ERocca_(WMF)> from SRE and
>> Majavah <https://en.wikipedia.org/wiki/User:Majavah> for their help
>> on finding and resolving deployment issues.
>> -
>>
>> Dan <https://www.mediawiki.org/wiki/User:Dzduvall> and Jeena
>> <https://www.mediawiki.org/wiki/User:JHuneidi_(WMF)> from Release
>> Engineering for help with build tooling.
>> -
>>
>> Guillaume <https://www.mediawiki.org/wiki/User:GLederrey_(WMF)> and
>> the rest of the Search Platform team for supporting our search index needs.
>> -
>>
>> Manuel for supporting our database needs.
>> -
>>
>> Niklas <https://meta.wikimedia.org/wiki/User:Nlaxstrom-WMF> and the
>> whole translatewiki.net community for help with localization and
>> internationalization.
>> -
>>
>> Rita <https://meta.wikimedia.org/wiki/User:RHo_(WMF)>, Olga
>> <https://meta.wikimedia.org/wiki/User:OTichonova_(WMF)>, Alex
>> <https://meta.wikimedia.org/wiki/User:AHollender_(WMF)>, and Matthew
>> <https://meta.wikimedia.org/wiki/User:MWilliams_(WMF)> from the Product
>> Design <https://www.mediawiki.org/wiki/Design> team for their
>> feedback on the Toolhub user interface.
>> -
>>
>> Scott <https://www.mediawiki.org/wiki/User:SBassett_(WMF)> from the
>> Security team for our security readiness review.
>> -
>>
>> Amire <https://en.wikipedia.org/wiki/User:Amire80>, Kunal, Eran,
>> Reedy, and Dan for contributing code to the project.
>> -
>>
>> Ricordisamoa <https://meta.wikimedia.org/wiki/User:Ricordisamoa>, Quim
>> <https://meta.wikimedia.org/wiki/User:Qgil-WMF>, and the people
>> participating in conversations on wikitech-l
>> <https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>
>> for T115650 <https://phabricator.wikimedia.org/T115650> which
>> inspired this whole project.
>> -
>>
>> Finally, a huge thanks to all the folks who gave input and feedback
>> on the talk page, in Phabricator, and at sessions - this is really
>> appreciated!
>>
>>
>> We hope that this new resource will be fun to explore, inspire you with
>> new ideas, and ultimately be useful for your work.
>>
>> Feedback, bug reports, ideas and questions are more than welcome on the talk
>> page of the project <https://meta.wikimedia.org/wiki/Talk:Toolhub>, or
>> in Phabricator <https://phabricator.wikimedia.org/project/board/3224/>.
>> Bryan (tech lead) & Seve (our new Product Manager) will be there to chat
>> with interested folks and help with any questions. We are looking
>> forward to evolving this project step-by-step and jointly with everyone!
>>
>> Birgit – on behalf of Technical Engagement & our Toolhub project team
>>
>>
>> --
>> Birgit Müller (she/her)
>> Director of Technical Engagement
>>
>> Wikimedia Foundation <https://wikimediafoundation.org/>
>> _______________________________________________
>> Wikimedia-l mailing list -- wikimedia-l(a)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…
>> To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org
>
> _______________________________________________
> Wikimedia-l mailing list -- wikimedia-l(a)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…
> To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org
--
Samuel Klein @metasj w:user:sj +1 617 529 4266
Dear Wikitech/Wikitech-Ambassadors,
Over the last few months, a small team at the Wikimedia Foundation has been
working on a project that has been discussed by many people in our movement
for many years: building ‘enterprise grade’ services for the high-volume
commercial reusers of Wikimedia content. I am pleased to say that in a
remarkably short amount of time (considering the complexity of the issues:
technical, strategic, legal, and financial) we now have something worthy of
showing to the community, and we are asking for your feedback. Allow me to
introduce you to the Wikimedia Enterprise API project – formerly codenamed
“okapi”.
While the general idea for Wikimedia Enterprise predates the current
movement strategy process, its recommendations [0] identify an enterprise
API as one possible solution to both “Increase the sustainability of our
movement” and “Improve User Experience.” That is, to simultaneously create
a new revenue stream to protect Wikimedia’s sustainability, and improve the
quality and quantity of Wikimedia content available to our many readers who
do not visit our websites directly (including more consistent attribution).
Moreover, it does so in a way that is true to our movement’s culture: with
open source software, financial transparency, non-exclusive contracts or
content, no restrictions on existing services, and free access for
Wikimedia volunteers who need it.
The team believes we are on target to achieve those goals and so we have
written a lot of documentation you get your feedback about our progress and
where it could be further improved before the actual product is ‘launched’
in the next few months. We have been helped in this process over the last
several months by the approximately 100 individual volunteers (from many
corners of the wikiverse) and representatives of affiliate organisations
who have reviewed our plans and provided invaluable direction. Pointing out
weaknesses and opportunities, or areas lacking clarity and documentation in
our drafts.
A essay describing the “why?” and the “how?” of this project is now on
Meta:
https://meta.wikimedia.org/wiki/Wikimedia_Enterprise/Essay
Also now published on Meta are an extensive FAQ [1] and operating
principles [2]. Much of this documentation is already available in French,
German, Italian, and Spanish.
For technical specifics, the new documentation on MediaWiki.org describes
the product strategy and roadmap, work currently underway, design
documents, as well as infrastructure decisions and future plans:
https://www.mediawiki.org/wiki/Wikimedia_Enterprise
The team is particularly interested in your feedback on how we have
designed the checks and balances to this project - to ensure it is as
successful as possible at achieving those two goals described above while
staying true to the movement’s values and culture. For example: Is
everything covered appropriately in the “Principles” list? Is the technical
documentation on MediaWiki.org clear? Are the explanations in the “FAQ”
about free-access for community, or project’s legal structure, or the
financial transparency (etc.) sufficiently detailed?
Meet the team and Ask Us Anything:
The central place to provide written feedback about the project in general
is on the talkpage of the documentation on Meta at:
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Enterprise
Equally, for technical comments or questions the talkpage on MediaWiki.org:
https://www.mediawiki.org/wiki/Talk:Wikimedia_Enterprise
<https://meta.wikimedia.org/wiki/Talk:Wikimedia_Enterprise>
On this Friday (March 19) we will be hosting two “Office hours”
conversations where anyone can come and give feedback or ask questions:
- 13:00 UTC via Zoom at https://wikimedia.zoom.us/j/95580273732
- 22:00 UTC via Zoom at https://wikimedia.zoom.us/j/92565175760 (note: this
is Saturday in Asia/Oceania)
Other “office hours” meetings can be arranged on-request on a technical
platform of your choosing; and we will organise more calls in the future.
We will also be attending the next SWAN meetings (on March 21)
https://meta.wikimedia.org/wiki/Strategic_Wikimedia_Affiliates_Network, and
also the next of the Wikimedia Clinics
https://meta.wikimedia.org/wiki/Wikimedia_Clinics
Moreover, we would be very happy to accept any invitation to attend an
existing group call that would like to discuss this topic (e.g. an
affiliate’s members’ meeting).
On behalf of the Wikimedia Enterprise team,
*Liam Wyatt [Wittylama]*
WikiCite <https://meta.wikimedia.org/wiki/WikiCite> Program Manager & Wikimedia
Enterprise <https://meta.wikimedia.org/wiki/Okapi> Community Liaison
Wikimedia Foundation
[0]
https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Recomme…
[1] https://meta.wikimedia.org/wiki/Wikimedia_Enterprise/FAQ
[2] https://meta.wikimedia.org/wiki/Wikimedia_Enterprise/Principles
Dear all,
It’s time for our third edition of the Coolest Tool Award!
Tools play an essential role at Wikimedia, and so do the many volunteer
developers who experiment with new ideas, develop & maintain local &
global solutions and enhance the experience for Wikimedia communities.
We’d like to invite you all to nominate your favorite & most used tools
and help us celebrate the people who create them!
As no one can possibly know all the cool tools out there, we’re looking
for some help and inspiration: please point us to the tools that you
think are great - for any reason you can think of!
Please go to https://meta.wikimedia.org/wiki/Coolest_Tool_Award
to recommend tools by October 27, 2021. You can nominate as many tools
as you want by filling out the form multiple times.
Thank you very much for your ideas & recommendation(s)!
The award is organized & selected by the Coolest Tool Academy 2021. We
plan to recognize the greatest tools in a variety of categories (for
examples, see last year’s categories). The award ceremony will take
place virtually again this year and we will provide more details soon
about the specific logistics and dates.
We will continue to spread the word over the next week, but if you get
the chance, please feel welcome to share this information with others
too!
Thanks :-)
Andre, for the Coolest Tool Academy 2021
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
TLDR: If you use "hard refresh" in your browser after editing a CSS or JS
page on the wiki, I'd like to hear about it so as to figure out whether
there may be a bug in the software. Please do test and confirm it for
yourself once more without a hard refresh, as it might just be an old habit
acting as a placebo :)
-
The "clearyourcache" message is the message that, contrary to its interface
key, instructs users to perform a page refresh in order to see the effect
of their edit to JS and CSS-related pages. For example:
https://translatewiki.net/wiki/MediaWiki:Clearyourcache/enhttps://en.wikipedia.org/wiki/MediaWiki:Common.csshttps://meta.wikimedia.org/wiki/MediaWiki:OSM.jshttps://meta.wikimedia.org/wiki/User:Krinkle/global.jshttps://en.wikipedia.org/wiki/MediaWiki:Citoid-template-type-map.json
As I understand it, this message is no longer be needed. I'm not aware of
any scenario in which a page carries this message, and edits to the page in
question would propagate to the editor's browser sooner as result of
performing a "hard reload".
If you find yourself doing hard reloads, or know people that do, I'd love
to hear detailed examples of specific combinations of pages/wikis/browsers
where people do this.
I've detailed the technical reasons for why these (should) have no impact,
on Phabricator:
https://phabricator.wikimedia.org/T291744
-- Timo