Grants talk:Project/sek2016/Feature improvements to Wikimedia Programs & Events Dashboard
September 26 Proposal Deadline: Reminder to change status to 'proposed'
As posted on the Project Grants startpage, the deadline for submissions this round is September 26, 2017. To submit your proposal, you must (1) complete the proposal entirely, filling in all empty fields, and (2) change the status from "draft" to "proposed." As soon as you’re ready, you should begin to invite any communities affected by your project to provide feedback on your proposal talkpage.
Hello sek2016. Thanks a lot for your project proposal and for working so hard on the P&E Dashboard.
I am a heavy user of the P&E Dashboard, and I am especially interested in seeing this amazing resource be developed. I have a couple of questions, a mix of requests and clarification-needed points:
- You have listed 5 features on the proposal. Could you please refer to the pertaining GitHub issue?
- Could you please develop the rationale for each feature you are proposing to develop? More specifically, could you please explain how the Dashboard works now for each feature and what we would gain with what we are proposing? (For instance, as I use the Dashboard a lot, I understand clearly what we get from features 1, 3 and 4, but I am not sure about the other feature.)
- There are many things we'd like to see developed on the Dashboard --I have myself contributed a bit with some requests for enhancements on the GitHub and directly to Sage. Why did you choose these features and not others that could be developed? I am trying to get a sense of how you have come up with priorities.
- I was not sure how features you have listed connect to the answer you gave about the problem you are trying to solve (first question), that emphasizes edit-a-thons. Could you please develop how features you intend to develop are related to "rough edges and needed improvements" for running edit-a-thons?
- You have said the 5 features you have listed are "some" of the work you'd be doing. What are the other features you intend to work on? Are they on the GitHub?
- I am a bit concerned by the lack of a wider, deeper strategy for community engagement. The Dashboard is a new tool for non-EN communities, and it is not so well-known. It requires, furthermore, a lot of voluntary work for translation. I was involved with the launching of automatic resources from the Dashboard on Wikipedia in Portuguese. I don't believe any other community at this time has decided to adopt these automatic resources yet. What can be done better to engage users with the Dashboard?
I also want to see an explanation how those five features were chosen and generally I want to see some kind of plan of activities with a timeline as well as better measures of success. Ruslik (talk) 18:21, 15 October 2017 (UTC)
- Referring to the doubts #1 and #2, I have referenced the GitHub issues with the respective Features and their rationale under the same. For the 5th feature, additional information will be added to the fields not easily understood by the user.(discovered while user testing)
- Referring to doubt #3, I have chosen these features depending on the user requirements discovered during my previous user testing sessions.
- Referring to doubt #4, I'll start by working on the feature which will make it possible to create a lot of new Wikipedia accounts during the events like edit-a-thons from a single IP address. The Design improvements made by some of the features listed will make it easy for edit-a-thons organizers to use the Dashboard. I am planning to work on the Issue- Instructor should be able to add multiple Available Articles at the same time. This will quicken the process of adding available articles. One of the users Heather Hart said that We don't add currently if the number of articles is huge, So we just mention them on our Wikipedia Page.
- Referring to doubt #5, I will fix other major issues that are identified in user testing sessions, I don't know what all of these will be yet.
- Referring to concern #6, For engaging with the users, I have been connecting with users from various communities and would keep on increasing the awareness about the new features and the benefits of using the Dashboard.
- Referring to Ruslik's doubt, for identifying measures of success I will ask Edit-a-thon organizers who have used the Dashboard before to provide feedback on the improvements. -- sek2016(talk) 20:33, 21 October 2017 (UTC)
Eligibility confirmed, round 2 2017
We've confirmed your proposal is eligible for round 2 2017 review. Please feel free to ask questions and make changes to this proposal as discussions continue during the community comments period, through 17 October 2017.
The committee's formal review for round 2 2017 begins on 18 October 2017, and grants will be announced 1 December. See the schedule for more details.Questions? Contact us.
FYI: I moved the page
Just a quick heads-up that I noticed that there was an extra space before the page title of Grants:Project/_Feature_improvements_to_Wikimedia_Programs_&_Events_Dashboard, so I took the liberty of redirecting it (and this talk page) to the current, corrected, page title. I left a redirect behind, so the page move shouldn't disrupt anything or confuse anyone. Jtmorgan (talk) 18:14, 21 October 2017 (UTC)
Aggregated feedback from the committee for Feature improvements to Wikimedia Programs & Events Dashboard
|(A) Impact potential
|(B) Community engagement
|(C) Ability to execute
|(D) Measures of success
|Additional comments from the Committee:
Response to the feedback
Regarding the Community Engagement
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's why I have not emphasized much on additional community engagement.
Regarding the Overall Measure of Success
I have mentioned that 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. Also, once i solve the listed issues, I will fix other major issues that are identified in user testing sessions, I don't know what all of these will be yet and their complexities. So, I cannot provide definite numbers.
This proposal has been recommended for due diligence review.
The Project Grants Committee has conducted a preliminary assessment of your proposal and recommended it for due diligence review. This means that a majority of the committee reviewers favorably assessed this proposal and have requested further investigation by Wikimedia Foundation staff.
- Aggregated committee comments from the committee are posted above. Note that these comments may vary, or even contradict each other, since they reflect the conclusions of multiple individual committee members who independently reviewed this proposal. We recommend that you review all the feedback and post any responses, clarifications or questions on this talk page.
- Following due diligence review, a final funding decision will be announced on March 1st, 2019.
Round 2 2017 decision
Congratulations! Your proposal has been selected for a Project Grant.
The committee has recommended this proposal and WMF has approved funding for the full amount of your request, 7200 USD
- You will be contacted to sign a grant agreement and setup a monthly check-in schedule.
- Review the information for grantees.
- Use the new buttons on your original proposal to create your project pages.
- Start work on your project!
Request for extension
Request for a change to the completion date and start date for my grant
- The new proposed completion date will be 31 August 2018, and the corrected start date will be 6 June 2018.
- I require an extention because I had my karate black belt exam in April and training was tougher than I expected. I submitted few code patches in March and after that was not able to produce quality work. I request WMF to adjust the reporting schedule of my project So that I have enough time to finish my final report.