current plans from the meeting logs:

• ibus-kkc
  {{{
  06:28:38 <tagoh_> dueno: how about ibus-kkc?
  06:28:46 <pravins> kkc?
  06:29:22 <tagoh_> pravins: yet another japanese engine he is developing
  06:29:39 <dueno> maybe I'll file a feature for it, whether or not it will be the default
  06:30:30 <dueno> (with libanthy compat wrapper, perhaps)
  }}}

• lohit fonts
  {{{
  06:33:19 <pravins> tagoh_: not any clear idea yet. But i would like to improve Lohit fonts hinting with ttfautohint
  06:33:50 <pravins> presently we are using autohint for Lohit in fedoa
  06:33:53 <pravins> Fedora
  06:34:14 <pravins> i am planning this in upstream project. i.e. ttfautohint lohit fonts .ttf
  06:34:48 <mfabian> pravins: does using ttfautohint actually make a difference on systems which can use the runtime autohinting of freetype? Isn't this the same result in the end?
  06:35:16 <pravins> mfabian: indeed, i think ttfautohint uses same program
  06:35:43 <pravins> it might be not impact Lohit output on Fedora much, but will definitely help to project using Lohit as a web fonts.
  06:36:32 <mfabian> pravins: yes, where freetype is not used for rendering, it should help.
  06:36:40 <pravins> mfabian: again, we will test it with xmag ;)
  }}}

from the discussion in the 2013-01-10 meeting:
* ibus-typing-booster
{{{
* IDEA: f19 feature: ibus-typing-booster to have predictive text
feature in English and n-gram support (tagoh_, 06:26:20)
* IDEA: f19 feature: ibus-typing-booster to default for inscript
engines (tagoh_, 06:27:53)
}}}

• ibus-kkc
  {{{
  06:28:56 <tagoh_> dueno: any comments about kkc?
  06:30:11 <dueno> tagoh_, will create a draft form soon (and make the initial release as well...)
  }}}

From today's meeting, no plans to submit features for Lohit and ibus-typing-booster. but I'll keep this open until the deadline is coming.

the feature planning phase has been finished. closing.