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?

Relevant background. This project has been mentioned at

http://www.mediawiki.org/wiki/Language_portal
http://www.mediawiki.org/wiki/Pune_LanguageSummit_February_2013/Event_Report#Language_Coverage_Matrix

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!

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!

GSoC "soft pencils down" date was yesterday and all coding must stop on 23 September. Has this project been completed?

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

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.

(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?

(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?

Harsh: What is missing here?

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.

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.