Hello everyone,
Some of you might know me already but I will still reintroduce myself. I am Satdeep Gill and I work in the Community Programs (GLAM) team at the Wikimedia Foundation, and my work is heavily focused on supporting Wikisource. I have been working on documenting various pain points and case studies around Wikisource and I will be coordinating with the Community Tech team if any of the Wikisource-related proposals <https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource> get voted among the top 5 in Community Wishlist Survey 2020 <https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020>. Voting began yesterday and will run until December 2, 2019. As you already know, 2020’s Community Wishlist Survey will be focused on Wikimedia projects other than Wikipedia, Commons and Wikidata. The Community Tech team at the Foundation will then work on the top 5 proposals voted by the community. This means that there is a significant chance that Wikisource will be receiving more attention this year! To support this process, I wanted to share some potentially helpful context gathered from my time talking with Wikisource communities in India. Based on a workshop I participated in recently with the Indic community at Wiki Advanced Training 2019 <https://meta.wikimedia.org/wiki/CIS-A2K/Events/Wiki_Advanced_Training/2019> organized by CIS-A2K <https://meta.wikimedia.org/wiki/CIS-A2K>, I have created a list of top priorities for the Indic Wikisource community. This might be useful to the global Wikisource community in evaluating Wishlist proposals, and I have identified specific proposals that closely match these priorities. They are: 1. Tools/scripts across various Wikisources - There are many scripts/tools that exist on some Wikisources and not on others. There isn’t enough documentation available to easily localize and integrate them in other Wikisources. (Similar to the proposal Migrate_Wikisource_specific_edit_tools_from_gadgets_to_Wikisource_extension 2020 proposal <https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource#Migrate_Wikisource_specific_edit_tools_from_gadgets_to_Wikisource_extension> ) 2. VisualEditor for Wikisource/Improving the Proofreading Interface - Wikisource uses a lot of templates and VisualEditor for Wikisource needs to be designed accordingly. (Similar to UI_improvements_on_Wikisource 2020 proposal <https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource#UI_improvements_on_Wikisource> ) 3. Tool to integrate book viewing with pagelist creation and identity page scan errors - the workflow for creating pagelist could be improved by an integrated bookviewer for PDF/DJVU files improving the page identification experience and allowing for adding/removing errored pages from a scanned file. (Similar to the proposal Index creation wizard 2020 proposal <https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource#Index_creation_wizard> ) Check the entire report from the Wiki Advanced Training at the link given below: https://outreach.wikimedia.org/wiki/GLAM/Newsletter/October_2019/Contents/Wikisource_report Besides these, it might also be worthwhile to consider the following proposal around supporting inter-wiki links on Wikisource: - Inter-language_link_support_via_Wikidata 2020 proposal <https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource#Inter-language_link_support_via_Wikidata> Once again, don't forget to vote on your favorite proposals before December 2, 2019 as the Community Tech team will be working on the top 5 voted proposals. Feel free to reach out to me at [email protected], in case you want to discuss any of the above, or to further discuss needs and strategies for Wikisource. --- Regards, Satdeep -- Satdeep Gill (pronouns - he, him) Program Officer GLAM and Underrepresented Knowledge Wikimedia Foundation <https://wikimediafoundation.org/>
_______________________________________________ Wikisource-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikisource-l
