Thank you for your response Srishti. I'll read through the article and get back to you if I have any questions, suggestions or concerns.
--- Tochi On Fri, Aug 30, 2024, 12:55 AM Srishti Sethi <[email protected]> wrote: > Hello all, > > Thank you so much for taking the time to review the proposal and for > sharing your thoughts and questions. Please see my response inline. > > On Tue, Aug 27, 2024 at 5:25 AM Sotiale Wiki <[email protected]> wrote: > >> I haven't read the details so I don't know the criteria for the random >> samples that the feature shows, but if we rule out other criteria, it looks >> like rsk, tdd definitely meet the community sustainability criteria. I >> think it's probably just a list of the most likely ones in ascending order. >> But this alone could be very useful. It's definitely more convenient than >> having to manually check recent activity all the time. >> > > That's very helpful to hear that metrics like this could be useful tools > for monitoring activity. > > >> On Mon, Aug 26, 2024 at 9:29 PM Denis Smajlović <[email protected]> wrote: > > I am unable to get an overview of the exact changes that you are proposing >> to the process. I am specifically interested in: > > Why does the current system not work? > > What specific changes do you suggest be implemented? > > > > Thanks for your question! This experiment addresses the issue of languages > spending many years in the Incubator before they can graduate, as well as > the technical challenges they face while editing. The technical challenges > faced by contributors to small language versions of Wikipedia are also > highlighted in the Language Diversity Hub’s research findings < > https://commons.wikimedia.org/wiki/File:Barriers_experienced_by_contributors_to_small_language_versions_of_Wikipedia.pdf>. > This experiment is a step forward, aiming to understand whether granting 5 > test wikis (that meet the experiment’s selection criteria) access to their > own Wikipedia sites and domains improves their editing experience compared > to when they were in the Incubator. Specifically, it seeks to determine if > access to modern wiki features that are available to Wikimedia wikis (e.g., > Content Translation, Wikidata) play a role in their editing productivity. > > 2024년 8월 27일 (화) 오전 5:51, Tochi Precious <[email protected]>님이 작성: >> > I've checked through the criteria, and I have nothing more to add but a >> suggestion: >> Why don't you also make it a combination of recently added wikis, as well >> as the older wikis. I noticed that the most recent one in the list has >> spent at least 2yrs in the incubator, maybe something a year or less. I >> would also like to see the kind of results this will produce. > > > Thanks, Tochi, for your suggestion! For this experiment, the curated list > of 35 languages meeting the inclusion and selection criteria ranges from 6 > months to 16 years in the Incubator, with only 6 of these wikis having > spent slightly less than 2 years. Since we need 5 wikis for the pilot, we > have formed 5 clusters of languages ranging from low to mid to high > activity (and across all time periods), with one language randomly selected > from each cluster. We will observe the impact of the treatment at the > cluster level and determine how this varies depending on the activity level > of the project. Given the way we are clustering data and forming sets of > languages, with each cluster meeting a specific set of criteria, it is > essential to select a different language if we were to choose from within > the same cluster. Regarding the 2-year time period, the closest we have is > Pannonian Rusyn, which is about 2.24 years old. > > We have also published a report about the methodology used, various > approaches considered, and how we reached the current set of languages at < > https://analytics.wikimedia.org/published/reports/languages_onboarding_experiment/1b_group_select.html>. > For a quick read, you can refer to the “Background” and “Approach” sections > and summary in the “Clustering” and “Sampling” sections. > > We would like to hear any more thoughts and suggestions preferably by the > end of this week! > > Cheers, > Srishti > > On Thu, Aug 22, 2024, 4:52 PM Srishti Sethi <[email protected]> wrote: >>> >>>> Hello Language Committee, >>>> >>>> I am writing today to share a proposal for an experiment addressing a >>>> new approach to onboarding a language wiki. >>>> >>>> Since December 2023, we have had conversations with 35 relevant >>>> stakeholders, including three members from the Language Committee (Tochi, >>>> Mf-Warburg, and Jon), to develop recommendations addressing a few current >>>> challenges with the incubation journey. As a result of these discussions, >>>> several recommendations emerged, which are documented here >>>> https://www.mediawiki.org/wiki/Future_of_Language_Incubation/Recommendations >>>> which can be broadly grouped into the following two key areas: >>>> >>>> 1. >>>> >>>> Streamlining technical infrastructure >>>> 2. >>>> >>>> Exploring social pathways >>>> >>>> >>>> For the 2024-25 annual planned work of the Wikimedia Foundation and as >>>> part of the Content Growth objective (WE2/Knowledge Equity) >>>> <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2024-2025/Goals/Equity#Closing_Knowledge_Gaps>, >>>> the Language and Product Localization team with guidance from the Language >>>> Committee members, identified a recommendation that addresses some of the >>>> difficulties of content creation in the Incubator due to technical >>>> limitations of the platform. To address this, we would like to try the >>>> following: >>>> >>>> Identify a set of requests (maximum 5) from the list in the new wiki >>>> approval backlog which have been either already approved by the Language >>>> Committee and, prioritize their creation on the production infrastructure >>>> so that they do not have to continue writing content on the incubator wiki. >>>> At the end of a stipulated period we evaluate progress of these prioritized >>>> wikis compared to other test projects (approved or otherwise) still in the >>>> incubator. >>>> >>>> Please see the detailed proposal >>>> <https://docs.google.com/document/d/1wpwimVyhLOJVMnIos4cAAquTglbjdKfiHcdUmHROc3s/edit?usp=sharing>, >>>> including selection and inclusion criteria, timeline, implementation plan, >>>> and more information. We also presented this proposal at Wikimania 2024: >>>> https://youtu.be/BbGrkYK8FEk?t=20299 >>>> >>>> After consultations with several other teams inside the WMF relevant to >>>> this area of work we believe this is a feasible starting point towards >>>> better content creation experiences for newer communities. To move onwards >>>> we would like to reach a shared agreement with the Language Committee and >>>> start off the pilot. Based on the criteria listed in the email, we would >>>> like to include as part of the experiment following list of wikis (also see >>>> attached screenshot): >>>> >>>> >>>> >>>> - >>>> >>>> Mapudungun >>>> - >>>> >>>> Southern Ndebele >>>> - >>>> >>>> Obolo >>>> - >>>> >>>> Tai Nüa >>>> - >>>> >>>> Pannonian Rusyn >>>> >>>> >>>> We would like to kick off this experiment as early as possible and >>>> would really appreciate hearing your suggestions on changes or additions to >>>> the selection criteria and initial list of wikis by August 24th. >>>> >>>> Cheers, >>>> >>>> Srishti >>>> >>>> *Srishti Sethi* >>>> Senior Developer Advocate >>>> Wikimedia Foundation <https://wikimediafoundation.org/> >>>> [image: screenshot_from_2024-08-07_19-41-25.png] >>>> _______________________________________________ >>>> Langcom mailing list -- [email protected] >>>> To unsubscribe send an email to [email protected] >>>> >>> _______________________________________________ >>> Langcom mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> >> _______________________________________________ >> Langcom mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> >
_______________________________________________ Langcom mailing list -- [email protected] To unsubscribe send an email to [email protected]
