Upgrade and enhance the ProveIt gadget, and spread it to more Wikipedias.
In 2016 I got a grant to enhance the ProveIt gadget which I completed successfully. Since then, I've done some improvements to the gadget but slowly the backlog has been growing. Furthermore, I expected the use of the gadget to decline because of the arrival of the new wikitext editor, which the gadget doesn't support (yet). However, the gadget usage has only increased (as can be inferred by comparing the numbers in my final report and the current ones) and has helped editors create tens of thousands of high-quality references.
Due to the sustained use and positive impact of the gadget, I think it's important to upgrade and enhance it so that it can continue serving editors well into the future, and also spread it to new Wikipedias that still don't have it available.
Tell us how you'll carry out your project. What will you and other organizers spend your time doing?
- Make the gadget work with the new wikitext editor
- Make the gadget work with the visual editor
- Make the gadget work when viewing pages, not just when editing, thus helping fulfill item #17 of the Community Wishlist Survey 2019: Mini-editor for citations
- Make the gadget work for Bibliography sections, not just references
- Develop a bot or some other automated solution for keeping the translations updated. Currently the gadget has been translated to over 90 languages at translatewiki.net. However, the gadget loads its strings from JSON pages in the MediaWiki namespace at Commons. So far these pages have been created and updated manually, so the difference between the quantity and quality of the translations at translatewiki.net and Commons is always growing. An automated solution is needed. This solution will be made generic so that other similar gadgets or projects can re-use it, and I will add it to the learning pattern I made for my first grant.
- Spread the gadget to as many new Wikipedias as possible
- Fix as many bug reports as possible
- Implement as many feature requests as possible
How will you let others in your community know about your project (please provide links to where relevant communities have been notified of your proposal, and to any other relevant community discussions)? Why are you targeting a specific audience?
- Left a message on the talk page of the gadget documentation of every Wikipedia that has one, which I have meticulously tracked here
- Left a message on the talk page of the WikiProject Source Metadata and the talk page of WikiCite
- Left a message on the discussion section of the Community Wishlist Survey 2019, item #17: Mini-editor for citations
- Left a message on the technical village pump of Spanish Wikipedia and the technical village pump of the English Wikipedia
- Notified past and present collaborators: Iniquity, Mattflaschen and Bastenbas
- Notified the executive director of my local Wikimedia Chapter, Anna Torres (WMAR)
What will you have done at the end of your project? How will you follow-up with people that are involved with your project?
- I will have done most if not all the tasks described above
- Follow-up will be done through the Phabricator project and the talk pages of the gadget documentation on each wiki
How will you know if the project is successful and you've met your goals?
- Compatibility with the visual editor
- Compatibility with the new wikitext editor
- Compatibility with the read mode
- Compatibility with the bibliography sections
- Number of new wikis adopting the gadget
- Number of new users adopting the gadget
- Number of feature requests closed
- Number of bug reports closed
What resources do you have? Include information on who is the organizing the project, what they will do, and if you will receive support from anywhere else (in-kind donations or additional funding).
- Myself, my computer, my skills and background. I will not receive any support from anywhere else.
What resources do you need? For your funding request, list bullet points for each expense:
- 2000 USD for two months of development time
- proven capable editor and developer of this tool. Valuable goals that tackle several requests in phabricator, that are unlikely to be fulfilled in the short term by the core software. —TheDJ (talk • contribs) 21:15, 4 February 2019 (UTC)
- +1 —MarcoAurelio (talk) 21:20, 4 February 2019 (UTC)
- Strong support This tool is very useful for editors.-Jayprakash >>> Talk 22:49, 4 February 2019 (UTC)
- Strong support This tool complements perfectly the editor. It saves me many time when I edit and I am sure that if Sophivorus make all the proposed changes, ProveIt will be better in all aspects. Good luck with the grant and the future development, I'm excited! Regards, Ivanhercaz (talk) 03:10, 5 February 2019 (UTC)
- Support The tool is quite invaluable in adding reference as well as in updating and correcting the ones already in an article. –Ammarpad (talk) 16:00, 7 February 2019 (UTC)
- Of course Strong support . Really useful tool with a lot of requests in the phabricator. Iniquity (talk) 07:58, 8 February 2019 (UTC)
- Of course! Support Winged Blades of Godric (talk) 18:00, 12 February 2019 (UTC)
- Support really useful and it'd be a good thing to upgrade it to the recent Mediawiki improvements. And wider adoption in language Wikipedias. Kpjas (talk) 08:47, 18 March 2019 (UTC)
- Strong support Excellent tool. ProveIt would provide strong pull to the new wikieditor if the grant were made to extend its functionality to work with the new wikieditor. Also, adding more built in archiving functionality can help with preventative link-rot protection. -Furicorn (talk) 04:18, 26 March 2019 (UTC)
- Support I love this tools, it prevent me doing function error like when I do reference adding manually.--AldNonymousBicara? 04:20, 26 March 2019 (UTC)
- Support ProveIt is popular in the English wiki medicine community. Blue Rasberry (talk) 13:55, 31 May 2019 (UTC)
- Strong support Very useful tool in spanish Wikipedia; it makes easy and fast the work of adding references. LuisCG11 (talk) 20:46, 12 June 2019 (UTC)
- Strong support Especially if you can make it less CPU intensive on the client side, and improve its ability to detect duplicate res. Guarapiranga (talk) 01:06, 23 October 2019 (UTC)