Page MenuHomePhabricator

jQuery.IME improvements
Closed, InvalidPublic

Description

After the feedback of the first release we have a good idea of what would need to be done in a next release. The main improvements would be to add an onscreen keyboard feature, support for content editable Divs and better browser compatibility.

This is a report to track the progress of this project proposed by the Language team at http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#jQuery.IME_next_big_release_improvements

(The title is mine. Plain "improvements" project ideas e.g. "go through the list of open bugs" are a hard sell in GSOC. Thank you for your understanding.)

Also note that jQuery.IME seems to use https://github.com/wikimedia/jquery.ime/issues as primary or parallel bug tracker.


Version: unspecified
Severity: enhancement
Whiteboard: gsoc
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=42373

Details

Reference
bz46660

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:26 AM
bzimport set Reference to bz46660.
bzimport added a subscriber: Unknown Object (MLST).

ankitgadgil wrote:

Hi, I am applying for Google Summer of Code 2013 with this as my project.
I have drafted a proposal for the same on my user page at
http://www.mediawiki.org/wiki/User:Ankitgadgil

I request you to go through it.
Suggestions or feedback of any kind are welcomed.

Thanks,
Ankit Gadgil

nithin111 wrote:

Hi,I have drafted a proposal for this project at www.mediawiki.org/wiki/User:Diadara536/GSoC
Here's my melange proposal link
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/diadara/12001#c14001
Any feedback is welcome

Just a note to say that Siddha Ganju has submitted a proposal related to this report: https://www.mediawiki.org/wiki/User:SiddhGanju/GSoC_2013_Application

Good luck to all candidates!

What should we do about this one now that gsoc is over?

This project seems to be an aggregation of bugs filed in GitHub. A possibility would be to promote the small bugs (2-3 hour of works of a seasoned contributor) as Google Code-in tasks before November 18:

https://www.mediawiki.org/wiki/Google_Code-In

What do you think?

We were already discouraging GSoC / OPW projects consisting in dealing with a collection of bug reports, as opposed to the development of a new feature. Maybe GCI is just better for this type of tasks.

I am closing this as non-actionable. The issues have been reported separately already as far as I know.