Last modified: 2014-03-21 08:54:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48651, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46651 - Language Coverage Matrix dashboard
Language Coverage Matrix dashboard
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Harsh Kothari
: analytics, i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-28 19:50 UTC by Quim Gil
Modified: 2014-03-21 08:54 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Quim Gil 2013-03-28 19:50:03 UTC
The Language Coverage Matrix dashboard would help automate the information about the languages supported by the Language Engineering tools, key maps, web fonts,  translation, language selector, i18n support for gender, plurals, grammar rules...

The LCM would display this information as well as provide visualization graphs of language coverage using various search criteria such as tools or languages. 

The developer on this project would build this web based dashboard using Javascript libraries integrated with MySQL to manage the data.

Proposed by the Language team at http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Language_Coverage_Matrix_dashboard
Comment 1 Quim Gil 2013-03-28 19:52:26 UTC
So basically this an optimized web view of
https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0Asnprhp63DAtdEQyTnMwV29yVFZFMmlwOXoxQU9SMFE#gid=0

right? Plus filtering and visualization features.
 
You mention MySQL. How would be the data introduced and would this be also part of the project? 

Would all this be content provided through a MediaWiki extension e.g. showing this dashboard in relation to a MediaWiki user profile or is it a stand-alone website not connected with MediaWiki?
Comment 3 Quim Gil 2013-04-29 17:44:21 UTC
Just a note to say that Harsh Kothari has submitted a GSoC proposar related to this report: https://www.mediawiki.org/wiki/User:Harsh4101991/GSoC_2013

Good luck!
Comment 4 Quim Gil 2013-05-01 17:33:19 UTC
Just a note to say that Parth Srivastav has submitted a GSoC proposal related to this report: http://www.mediawiki.org/wiki/User:Parth4992

Good luck!
Comment 5 Quim Gil 2013-09-17 16:13:05 UTC
GSoC "soft pencils down" date was yesterday and all coding must stop on 23 September. Has this project been completed?
Comment 6 Runa Bhattacharjee 2013-09-18 14:49:01 UTC
Hello, the functional deliverables from the original scope of the project have been completed and merged into the upstream repo[1]. Harsh is expected to write a bigger report and finish all the documentation before September 23rd. We do however expect to continue working on the project with Harsh to add some extended functionalities and innovations that were identified during the implementation. Thanks.

[1] https://github.com/wikimedia/lcm-dashboard/tree/gsoc2013
Comment 7 Quim Gil 2013-10-22 19:34:57 UTC
If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor.

We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks.

More information in the wiki page. If you have questions you can ask there or you can contact me directly.
Comment 8 Andre Klapper 2014-01-21 13:22:07 UTC
(In reply to comment #6)
> Hello, the functional deliverables from the original scope of the project
> have
> been completed and merged into the upstream repo[1]. Harsh is expected to
> write
> a bigger report and finish all the documentation before September 23rd. We do
> however expect to continue working on the project with Harsh to add some
> extended functionalities and innovations that were identified during the
> implementation. Thanks.

This makes me wonder what is missing to close this as FIXED or WORKSFORME. 
Could somebody clarify?
Comment 9 Andre Klapper 2014-02-26 16:45:47 UTC
(In reply to Runa Bhattacharjee from comment #6)
> Hello, the functional deliverables from the original scope of the project
> have been completed and merged into the upstream repo[1]. Harsh is expected
> to write a bigger report and finish all the documentation before September
> 23rd. We do however expect to continue working on the project with Harsh to
> add some extended functionalities and innovations that were identified
> during the implementation. Thanks.

This makes me wonder what is missing to close this as FIXED or WORKSFORME. 
Could somebody clarify?
Comment 10 Andre Klapper 2014-03-20 11:44:59 UTC
Harsh: What is missing here?
Comment 11 Quim Gil 2014-03-20 14:42:23 UTC
While I have seen this dashboard running (and also Harsh presenting it at FOSDEM)... Searching for it in mediawiki.org gives as a result an incomplete and virtually orphan page

https://www.mediawiki.org/wiki/Language_Coverage_Dashboard

that links to http://tools.wmflabs.org/lcm-dashboard/lcmd/ 

-----------------------------------

No webservice
The URI you have requested, http://tools.wmflabs.org/lcm-dashboard/lcmd/, is not currently serviced.

(...)

If you maintain this tool
You have not enabled a web service for your tool, or it has stopped working because of a fatal error. You may wish to check your logs or common causes for errors in the help documentation.

-----------------------------------

So yes, it would be good what is the current status of this project, whether it is indeed pending or those problems are just temporary and we can close this report.
Comment 12 Harsh Kothari 2014-03-21 08:54:20 UTC
This problem is temporary. I guess its working till 2nd of March. I will check it out. But this bug should be closed or fixed because functional deliverables are being implemented.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links