Page MenuHomePhabricator

Improve the year in review tool for next year
Open, Needs TriagePublic

Description

https://wikipediayir.netlify.app/ was made last year (in my volunteer capacity) to allow editors to see their contributions. Id like some help to make sure the next year's offering is even better!

Possible hackathon goals:

  • Add more interesting facts e.g. what time of day
  • improve performance by finding better suited APIs
  • better support for other projects e.g. wikidata

Event Timeline

Hi @Jdlrobson I noticed https://wikipediayir.netlify.app/ and it's pretty cool. Last year, I saw users proudly sharing their achievements from it on social media. I'm curious, why is this app still hosted on Netlify instead of moving to Toolforge?

Hi @Gopavasanth various reasons, but mainly because Toolforge does not have push to deploy and I do not like sysadmin responsibilities. If someone wanted to host it there as an alternative they are more than welcome :-)

@Jdlrobson can you help us find the codebase repo for the tool?

@Gopavasanth @Reputation22 and I will be working to implement the following:

  • Basic redesigning of the tool interface
    • Dropdown of wikis
    • Download image (apart from copy to clipboard)
  • Move repository to GitLab
  • Deploy on toolforge
  • Setup CI/CD for quicker deployments

Move repository to GitLab

I'm keen to keep the canonical repo on github if that's okay, but feel free to fork provided you push back :-)!

In the Wikimedia-Hackathon-2024, @theprotonade, @Reputation22, and I (@Gopavasanth) collaborated on enhancing the Year in Review tool originally developed by @Jdlrobson.

Here's what we accomplished:

  • Refactored and redesigned the tool for improved functionality.
  • Successfully migrated the repository to Gitlab for better collaboration.
  • Significantly enhanced the implementation.
  • Deployed the updated tool on Toolforge.
  • You can check out the tool at: https://yearinreview.toolforge.org/

And here's the link to the repository: https://gitlab.wikimedia.org/toolforge-repos/yearinreview

Thanks guys!!
Following back on the discussion which me and @theprotonade had. We can scale up the project, and have its discovery from Wikipedia Profile page.

What do you guys think? @Gopavasanth @Jdlrobson

This would be helpful for user engagement and growth for Wikimedia

Move repository to GitLab

I'm keen to keep the canonical repo on github if that's okay, but feel free to fork provided you push back :-)!

We can have a code mirror on Github, but the original repo should be in Gitlab (under toolforge-repos), for us to host under toolforge.
Also it would be nice to have all the tools inside toolforge, rather than relying on 3rd party service providers like netlify

This would be helpful for user engagement and growth for Wikimedia

+1; just chiming in to say it might be interesting to explore the idea of having this surfaced on Special:Homepage.

Thanks all for making these great changes to the UI!

The blockers for putting this somewhere more discoverable are all on the backend. In current form the tool must make an API call for every 500 edits, and every 5 log actions, so some new APIs would need to be built before we can even consider moving this code to production given we have editors that hit those limits in a single day and would require hundreds/thousands of HTTP requests.

Yeah agreed,
So apart from those, we planned to have one GET api (something along the lines of action=query & meta=userstories) which essentially collects user data and returns the data which we would want to showcase on client

This would be helpful for user engagement and growth for Wikimedia

+1; just chiming in to say it might be interesting to explore the idea of having this surfaced on Special:Homepage.

This sounds great, provided we get to a stable release with everything working as expected :)