What is the problem you're trying to solve?
It's hard to run editing events smoothly and keep track of the results. The dashboard has made a lot of progress in solving it, but for edit-a-thons there are still a lot of rough edges and needed improvements to make it an easy-to-use tool for anyone running an edit-a-thon or similar event.
What is your solution?
To build specific new features and improve known shortcomings like creating a lot of new Wikipedia accounts during the events like edit-a-thons from a single IP address. To allow users track their contributions easily by enhancing usability of Dashboard on the mobile devices. Along with user testing to identify further areas for improvement.
- Making the functioning related to organizing real time events such edit-a-thons hassle free.
- Ability of the users to track their contributions on their mobile devices.
How will you know if you have met your goals?
Creating a short video, for making users aware of all the new features. I plan on resolving at least 4 issues per week depending on the complexities involved and have 6 or more user testing sessions for verifying the problems solved.
Do you have any goals around participation or content?
The overall participation will increase with the growing features and enhanced usability of the dashboard.
I will carry out my project by actively working on the high priority tasks and on the side continuously making the improvements to enhance the usability of Dashboard on the mobile devices.
Some of the features I will work on:
- In mobile, making sure key information is accessible as the user scrolls - Work involves fixing the table header at the top when user scrolls it out of view with jQuery. GitHub Issue #1469
- Making available course access rights to the Education manager, So that they could support instructors - Work involves updating privileges of the Education Manager. GitHub Issue #1471
- On the My Dashboard Page, displaying the Archived programs in a way to make the newest information available first - Work involves changing the order of the programs from newest to oldest. GitHub Issue #1472
- After a course has ended, making available a way to track users by an instructor or admin - Could be solved by a way to direct instructors or admins to user profile pages. GitHub Issue #1307
- Displaying additional information for the components not clearly understood by the users - Work involves adding info icons with tooltips.
I plan on adding patches for these features within the first 3 weeks and getting them merged, as on the side I'll be working on mobile clean up. After that, I'll have time for tasks that I would discover via user testing.
I would have added important features, refined the user layout, published blogs and written documentation by the end of my project.
|Grantee||Role||Job description||Commitment||Person weeks||Cost|
||30 hrs/week||12 weeks(1)||7200 USD(2)|
- Based on salary of 20 USD/hr at 30 hrs/week. (Based on exchange rate of 1 USD = Rs 65.34 on 26 Sept 2017).
I am planning to engage the community by actively blogging about the new features added and enhancements made to the Dashboard.
- Volunteer I am happy to provide design feedback during this project, on an as-needed basis. Jtmorgan (talk) 21:29, 17 October 2017 (UTC)
I had previously communicated with various communities and met the active users of the Dashboard from those communities for understanding their requirements. I will follow the same methodology for this project.
The usage statistics of the Dashboard can be viewed on the Usage Stats Page. More than 7000 editors have logged in to and used P&E Dashboard. Sage mentioned that dashboard is already getting substantial suggestions from the community via the 'Report a problem' link. Considering the scale of use already happening and the high volume of actionable feedback, Dashboard has more things which are to be improved that we already know the community needs that can be handled. That's why I have not emphasized much on additional community engagement. I have mentioned the same on the talk page
Do you think this project should be selected for a Project Grant? Please add your name and rationale for endorsing this project below! (Other constructive feedback is welcome on the discussion page).
- Strong Support. Sejal has done outstanding work on the Dashboard during Outreachy and GSoC internships, and this is important work that would be left undone otherwise. I'll be delighted to do code review and provide other support for this project.--Ragesoss (talk) 19:45, 28 September 2017 (UTC)
- Strong Support Sejal is one of our remarkable Google Summer of Code students from 2017. I've got the opportunity to meet with her recently in-person at Wikimania, learn about her contributions, passion for the WikiEd Dashboard project. I think that her efforts will be a great addition to the project and the team -- Srishti Sethi (talk) 20:03, 17 October 2017 (UTC)
- Strong Support. I use Dashboard tool for all WikiDonne's events and I worked with Sejal during Wikimania 2017 Hackathon, creating a new model of course to keep trace of modifies done non only by user, but also on the articles assigned to the user. I see how she works and how she cares, in a wikimedian style, so I'm sure that will do a great job from wich all will benefit. Camelia (talk) 20:19, 17 October 2017 (UTC)
- Strong support. I was one of Sejal's mentors during her GSOC and Outreachy internships. She is an excellent developer and UI designer. She is also an excellent communicator, takes deadlines seriously, and has gained a great deal of experience with user research and usability testing. I am confident that she already knows a great deal about how to improve the dashboard to support edit-a-thons and how to make the mobile experience better for all users. And I'm also confident that she will be able to discover, prioritize, and address new ideas for features and functionality improvements that arise during her user testing sessions. Jtmorgan (talk) 21:26, 17 October 2017 (UTC)
- Strong support. This project proposal lays out much-needed, important work to improve Dashboard, an increasingly indispensable tool for outreach organization. I use the Outreach Dashboard weekly to train with public library staff -- her work would have immediate impact on many projects. It's clear from the proposal, and from meeting her at Wikimania, that Sejal has the expertise, experience and enthusiasm to get the job done. Shameran81 (talk) 18:49, 2 November 2017 (UTC)
- Support The P&E dashboard has more directly led to massive new donations and institutional investment in Wikimedia projects as compared to any other single wiki technological innovation of which I am aware. I support its continual development. I have to admit that I do not follow the technical proposals discussed in this grant, but considering the expertise gathered here, the low amount of funding requested, and the Dashboard's knockout history of bringing in external financial donations, participant engagement, media attention, and overall positive impact to Wikimedia projects, I support its development in all directions. Blue Rasberry (talk) 13:09, 8 November 2017 (UTC)
- Support The benefits and overall value of this proposal make it easy for me to support. Jackiekoerner (talk) 13:17, 12 November 2017 (UTC)