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
Hello all,
As you may know, the WikidataCon 2021 will take place online on October
29-31, and its program is built in two parts:
- on Day 1, *the main track
<https://www.wikidata.org/wiki/Wikidata:WikidataCon_2021/Program/Day_1_-_Mai…>*,
that will deliver plenty of curated presentations and keynotes from diverse
and interesting speakers, available to everyone in livestream ;
- on Day 2 and 3, *the community tracks
<https://www.wikidata.org/wiki/Wikidata:WikidataCon_2021/Program/Day_2_and_3…>*,
ten thematic tracks that will allow the registered participants to dive
deeper into multiple topics, share knowledge, present the latest updates of
their projects, run discussions and workshops related to sustainability,
GLAM, education and science, Wikibase, and plenty of other topics.
The call for proposals for the community program is still running and will
be open until October 20th midnight. However, as we are building a dynamic
schedule, we can already present you the *first beta version of the
schedule <https://pretalx.com/wdcon21/schedule/#2021-10-30>*.
This schedule is presenting the sessions that have already been submitted
and accepted by the community curators, and confirmed by the speakers. The
exact times and duration of the sessions may still evolve until the week of
the conference, depending on the new submissions we receive.
If you would like to contribute to the community program, if you have ideas
or suggestions, don’t hesitate to *submit sessions
<https://pretalx.com/wdcon21/submit/> as soon as possible and before
October 20th*, to make sure that we can include them in the program!
We will keep releasing beta versions of the schedule and its content will
still be very flexible until October 26th.
As a reminder, you can also book a slot for the birthday presents lightning
talks <https://www.wikidata.org/wiki/Wikidata:Ninth_Birthday> and if you
didn’t register for the WikidataCon yet, you can do it in 5 minutes here
<https://pretix.eu/WDCon21/WDCon21/>.
Thanks for reading this update! You can find out more about the WikidataCon
on this page <https://www.wikidata.org/wiki/Wikidata:WikidataCon_2021>, and
read the previous updates above. If you have any questions or suggestions,
feel free to reach out to us by leaving a comment on the talk page
<https://www.wikidata.org/wiki/Wikidata_talk:WikidataCon_2021#WikidataCon_up…>
or contacting info[image: at]wikidatacon.org.
For the WikidataCon organization team,
--
Léa Lacroix
Community Engagement Coordinator
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
The Wikipedia & Education User Group invites you to attend our next Open
Meeting via Zoom on Wednesday, October 13, from 4 pm UTC to 5:30 pm UTC
(see your time zone here: https://zonestamp.toolforge.org/1634140801).
As usual for our Open Meetings, we will provide updates from the Wikipedia
& Education User Group board, then leave most of the time for our guest
speakers.
Our guest speakers this month will be Amanda Rust and Amy Ruskin, who will
speak on their work with Wikidata in an educational library setting, and
Thomas Shafee, who will discuss the WikiJournals and their bridging of the
Wikipedia-academia divide.
Our speakers' biographies:
* Amanda Rust is the Associate Director for Services in the Digital
Scholarship Group in the Northeastern University Library. She’ll speak
about how Wikidata fits into an initiative to collaboratively document
neighborhood public art data in Boston. By focusing on public art outside
of more well-known downtown areas, this initiative hopes to highlight the
history of art and artists in historically marginalized neighborhoods.
* Amy Ruskin is the Data Engineer in the Digital Scholarship Group in the
Northeastern University Library. She will discuss the process of setting up
the Boston neighborhood public art project in Wikidata, including
determining data models and creating a WikiProject page.
* Thomas Shafee is an evolutionary biochemist and data scientist based at
La Trobe Uni in Australia. He'll talk on the work he does on bridging the
Wikipedia-academia divide by forming compatible interfaces between the ways
the two communities operate. As part of this, he chairs the WikiJournal
User Group, and is Editor in Chief of the WikiJournal of Science and an
editor for PLOS Genetics. Through these, non-Wikimedian scholars can write
new high-accuracy Wikipedia pages, and existing Wikipedia pages are put
through external peer review.
We hope you can join us!
The meeting will be hosted via this link:
https://us02web.zoom.us/j/81371223837?pwd=K3dQZnh3WU9TYTY3MzBOV1l4WnBiZz09
Meeting ID: 813 7122 3837
Passcode: 153195
If you would like to be added to the Google Calendar invite, please send me
an email offlist.
Hi everyone,
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month—but this month it's the
second Wednesday. Come talk to us about anything related to Wikimedia
search, Wikidata Query Service, Wikimedia Commons Query Service, etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, October 13th, 2021
Time: 15:00-16:00 GMT / 08:00-09:00 PDT / 11:00-12:00 EDT / 17:00-18:00 CEST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vgj-bbeb-uyi
Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927
*NOTE: We have a new Google Meet link as of August 2021, which offers
international calling options.*
Hope to talk to you next week!
—Trey
Trey Jones
Sr. Computational Linguist, Search Platform
Wikimedia Foundation
UTC–4 / EDT
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/
The Journal of Web Semantics (JWS) invites submissions for a special
issue on Community-based Knowledge Bases and Knowledge Graphs, edited by
Tim Finin, Sebastian Hellmann, and David Martin. (contact email:
cbkb(a)cs.umbc.edu <mailto:cbkb@cs.umbc.edu>) *Submissions are due by
November 01, 2021.* Please see the JWS post here:
http://www.websemanticsjournal.org/2021/06/cfp-community-based-knowledge-ba…
<http://www.websemanticsjournal.org/2021/06/cfp-community-based-knowledge-ba…>
Introduction
Community-based knowledge bases (KBs) and knowledge graphs (KGs) are
critical to many domains. They contain large amounts of information,
used in applications as diverse as search, question-answering systems,
and conversational agents. They are the backbone of linked open data,
helping connect entities from different datasets. Finally, they create
rich knowledge engineering ecosystems, making significant, empirical
contributions to our understanding of KB/KG science, engineering, and
practices. From here forward, we use "KB" to include both knowledge
bases and knowledge graphs. Also, "KB" and "knowledge" encompass both
ontology/schema and data.
Community-based KBs come in many shapes and sizes, but they tend to
share a number of commonalities:
*
They are created through the efforts of a group of contributors,
following a set of agreed goals, policies, practices, and quality norms.
*
They are available under open licenses.
*
They are central to knowledge-sharing networks bringing together
various stakeholders.
*
They serve the needs of a community of users, including, but not
restricted to, their contributor base.
*
Many draw their content from crowdsourced resources (such as
Wikipedia, OpenStreetMap).
Examples of community-based KBs include Wikidata, DBpedia, ConceptNet,
GeoNames, FrameNet, and Yago. This special issue will highlight recent
research, challenges, and opportunities in the field of community-based
KBs and the interaction and processes between stakeholders and the KBs.
We welcome papers on a wide variety of topics. Papers that focus on the
participation of a community of contributors are especially encouraged.
Topics of interest
We are looking for studies, frameworks, methods, techniques and tools on
topics such as the following:
*
The impact of community involvement on characteristics of KBs such
as requirements, design, technology choices, policies, etc. For
example, how are KB characteristics driven by the community and
reflective of the community's needs?
*
Conversely, the impact of KB characteristics on community
involvement. For example, how do changes in these characteristics
affect the participation and behavior of members of the community?
*
Organizational challenges and solutions in developing and managing
community-based KBs.
*
Technical challenges and solutions in community-based KBs,
concerning a technical area such as:
o
Representation of knowledge and logical foundations
o
Reasoning, querying, and constraint-checking
o
Knowledge acquisition
o
Knowledge preparation (e.g., cleaning, deduplication, alignment,
merging)
o
Maintaining consistency with external sources
o
Representing and managing metadata (including issues involved in
adding metadata to relation instances)
o
Provenance
o
Quality assurance
*
User interfaces and experience, both for contributing to the KB and
using it, by different user groups.
*
Implemented metrics and quality tests to guide the community in
improving KG quality and expanding KG coverage.
*
Achieving and managing knowledge diversity, for instance, in the
form of multilinguality, multi-cultural coverage, multiple points of
view, and a diverse and inclusive contributor base.
*
Detecting and avoiding malicious, inappropriate, and misleading
content in community-based KBs.
*
Biases in community-based KBs and their impact on downstream uses of
KB content.
*
Community-based KBs in science, medicine, law, government, or other
domains.
*
Handling specialized types of knowledge (such as commonsense,
probabilistic, or linguistic knowledge) in a community setting.
*
Methods and tools to manage KB evolution, including change
detection, change management, conflict resolution, visualization of
change history.
*
Tools and affordances supporting community or collaborative
activities, including discussions, feedback, decision making, task
allocation, etc.
*
Motivations and incentives affecting community participation.
*
Approaches and metrics for community health, including but not
restricted to community growth or diversity.
*
Roles and participation profiles in communities building and
maintaining KBs.
*
Frameworks and approaches to support group decision-making and
resolve conflicts.
Types of Papers
We invite submission of Research, Survey, Ontology, and System papers,
according to the guidelines given at https://www.jws-volumes.com
<https://www.jws-volumes.com/>.
Submission Guidelines
The Journal of Web Semantics solicits original scientific contributions
of high quality. Following the overall mission of the journal, we
emphasize the publication of papers that combine theories, methods and
experiments from different subject areas in order to deliver innovative
semantic methods and applications. The publication of large-scale
experiments and their analysis is also encouraged to clearly illustrate
scenarios and methods that introduce semantics into existing Web
interfaces, contents and services.
Submission of your manuscript is welcome provided that it, or any
translation of it, has not been copyrighted or published and is not
being submitted for publication elsewhere.
Manuscripts should be prepared for publication in accordance with
instructions given in the JWS guide for authors
<http://www.elsevier.com/journals/journal-of-web-semantics/1570-8268/guide-f…>.
The submission and review process will be carried out using Elsevier's
Web-based EM system
<https://www.editorialmanager.com/JOWS/default.aspx>. Please state the
name of the SI in your cover letter and, at the time of submission,
please select “VSI:CBKB” when reaching the Article Type selection.
Upon acceptance of an article, the author(s) will be asked to transfer
copyright of the article to the publisher. This transfer will ensure the
widest possible dissemination of information. Elsevier's liberalpreprint
policy<https://www.elsevier.com/authors/journal-authors/submit-your-paper/sharing-…>permits
authors and their institutions to host preprints on their web sites.
Preprints of the articles will be made freely accessible viaJWS First
Look
<https://papers.ssrn.com/sol3/JELJOUR_Results.cfm?form_name=journalbrowse&jo…>.
Final copies of accepted publications will appear in print and at
Elsevier's archival online server.
Important Dates
*
Submission deadline: November 1, 2021
*
Author notification: February 7, 2022
*
Minor revisions due: February 21, 2022
*
Major revisions due: March 14, 2022
*
Papers appear on JWS preprint server: May 2, 2022
*
Publication: Fall or Winter 2022
Guest Editors
Tim Finin is the Willard and Lillian Hackerman Chair in Engineering and
a Professor of Computer Science and Electrical Engineering at the
University of Maryland, Baltimore County (UMBC).
Sebastian Hellmann is the head of the “Knowledge Integration and
Language Technologies (KILT)" Competence Center at InfAI, Leipzig. He
also is the executive director and board member of the non-profit
DBpedia Association with over 30 key players
<https://www.dbpedia.org/members/overview/>in the knowledge graph area.
He earned a rank in AMiner’s top 10 of the most influential scholars in
knowledge engineering of the last decade.
David L. Martinis a Research & Development Scientist in Artificial
Intelligence. He has held positions at SRI International, Siri, Inc.,
Apple, Nuance Communications, Samsung Research America, and the
University of California at Santa Cruz. He is a Senior Member of the
Association for the Advancement of Artificial Intelligence, and
currently works as an independent consultant in Silicon Valley, California.