T91676 [Epic] Make the Education program dashboard usable for all languages and projects (original) (raw)
[Epic] Make the Education program dashboard usable for all languages and projects
- Edit Task
- Edit Related Tasks...
- Create Subtask
- Edit Parent Tasks
- Edit Subtasks
- Merge Duplicates In
- Close As Duplicate
- Edit Related Objects...
- Edit Commits
- Edit Mocks
- Mute Notifications
- Protect as security issue
Details:
- Primary mentor: @Ragesoss
- Co-mentor: @Capt_Swing
- Other mentors: (optional, Phabricator username)
- Skills: Ruby, Javascript / Coffeescript, React.js
- Estimated project time for a senior contributor: 3 weeks
- Microtasks: T114906, T114908, T114905
DESCRIPTION:
The Wiki Ed Dashboard is a Ruby on Rails app that runs dashboard.wikiedu.org ( source on GitHub). It's being built primarily by Wiki Education Foundation to support Wikipedia classroom projects in the United States and Canada, and it serves as a replacement for the EducationProgram extension. It could also be useful for the global Wikimedia community — both for education programs and for other projects where it's important to keep track of the on-wiki activity of a group over users over a certain time period. But it's been designed first and foremost for the specific, English-language, English-Wikipedia-focused needs of Wiki Education Foundation. So it will take some effort to turn it into a system that can serve users in any language and to work well in many different contexts.
Some of the basic i18n infrastructure is in place, but it is not used consistently throughout the codebase. There are also many features and configurations that are specific to Wiki Education Foundation's programs. So the baseline for making the dashboard usable across languages and programs is complete the i18n work, and add options to disable — or locally configure — the features that are specific to Wiki Education Foundation's programs. That would make it feasible to deploy a new dashboard for any language. Getting that far is a reasonable goal for an internship project.
FOLLOW-ON WORK:
From there, it's an open question how best to support many different languages at once. That could mean spinning up a separate instance of the dashboard for each language, which means that automating the deployment and update process would be an important next step. Or, it could mean improving the core dashboard to support many languages simultaneously.
Relevant future work:
- Consider making it work for multiple projects, rather than one instance per project.
- Verify that branding is consistent with WMF sites.
- Packaging and deployment.
PLAN:
- Convert all hard-coded English interface strings to use i18n messages
- Set up an instance on wmflabs.org for i18n testing, and work with Education Collaborative members to identify additional features need to be either disabled or generalized from their current Wiki Education Foundation-specific forms
- Add option to disable the 'Wizard' assignment design tool, the content of which is very specific to Wiki Education Foundation
- Add further configuration options to remove or generalize other features identified by Education Collaborative members
Additional working notes on the implementation:
https://etherpad.wikimedia.org/p/article.wiki
Event Timeline
There are a very large number of changes, so older changes are hidden. Show Older Changes
I am shifting this to Outreachy-Round-11 as the project description has two mentors, micro-tasks and looks ready for the 11th edition of Outreachy ( Dec 2015 - Mar 2016 ) . Potential candidates should start by submitting their proposals as a blocker for this task, by November 02.
Feel free to revert it back, if this task has some relevant issues which might block its completion in this term of Outreachy.
Anyone willing to organize a webinar and show us through the existing dashboard?
Education leaders from all over the world should get to know it better - and comment on it - before you decide to devote precious programming time to it. We are the potential users and IMHO should be involved in the decision process.
Thank you. Just watched the youtube video and it gave me a pretty good idea about the WikiEd Dashboard. I will sum up my points on the page linked by Tighe.
NOTE: Outreachy round 12 applications are now open and GSoC 2016 is round the corner. This project was featured for Outreachy round 11 and has a well defined scope. Are you ready to mentor the project this season? If yes, then we'll feature this for Outreachy round 12 and GSoC 2016 as well. Please reply back in comments.
Yes, that would be wonderful @Sumit! We didn't find any suitable participants in round 11 to take on this project but would love to feature it again and define the follow-up scope for this project for round 12 (we are currently working on some of this work during a sprint in February - but there's lots more to do and help would be appreciated!).
Poking @Abit because she should know about this. Also poking @Ragesoss and @dduvall, who graciously agreed to mentor and co-mentor a prospective Outreachy student.
Thank you for asking about this, @Sumit.
Yes, that would be wonderful @Sumit! We didn't find any suitable participants in round 11 to take on this project but would love to feature it again and define the follow-up scope for this project for round 12 (we are currently working on some of this work during a sprint in February - but there's lots more to do and help would be appreciated!).
Poking @Abit because she should know about this. Also poking @Ragesoss and @dduvall, who graciously agreed to mentor and co-mentor a prospective Outreachy student.
Thank you for asking about this, @Sumit.
Thats great news!
@Ragesoss , @dduvall are you willing to support this project for the upcoming round of GSoC/Outreachy programs?
awight renamed this task from [epic] Make the Education program dashboard usable for all languages and projects to [Epic] Make the Education program dashboard usable for all languages and projects.Feb 27 2016, 6:52 AM
@awight @AndyRussG @dduvall @Capt_Swing Are any of you up for co-mentoring with me on this? I can be the primary mentor. I think we've done enough of the groundwork on this project, thanks to the February sprint, that this would be a really good project for GSoC/Outreachy. There are also a couple of people who've expressed interest who seem likely to have the technical skills to dive into it, if selected.
@awight @AndyRussG @dduvall @Capt_Swing Are any of you up for co-mentoring with me on this? I can be the primary mentor. I think we've done enough of the groundwork on this project, thanks to the February sprint, that this would be a really good project for GSoC/Outreachy. There are also a couple of people who've expressed interest who seem likely to have the technical skills to dive into it, if selected.
@Pginer-WMF: same invitation as above... if you're interested in co-mentoring on this, let us know. :-)
As a reminder, GSoC application period starts on 14th March. It'd be great if this project could have a co-mentor. :)
At @Ragesoss's request, I just added myself as a mentor for UX related parts of the project. I look forward to helping!
At @Ragesoss's request, I just added myself as a mentor for UX related parts of the project. I look forward to helping!
Thank You @Capt_Swing , moving this to "featured for GSoC/Outreachy"
@Sumit hasn't the deadline for proposals already passed? I did take a pass at making sure all the remaining microtasks are still relevant.
Ah, yeah. I discussed tasks with Mary on GitHub (and we also met once in person), and she's now done three nice commits.
@Ragesoss , Outreachy-13 is soon to start, does this project still stand as a prospective internship project?
The main push for this is done. There are some edge cases — UI issues for wikidata, support for incubator and multilingual wikisource, and probably other similar cases — that we don't yet handle, but the known individual cases are being tracked separately.
The main push for this is done.
Well done! We're already reaping the benefits.
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits