Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2013-06-04 13:52:55
Size: 2609
Editor: OsamuAoki
Comment:
Revision 4 as of 2013-06-13 12:44:07
Size: 2998
Editor: OsamuAoki
Comment:
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
 * DebianPts:ibus and its family of of packages
 * DebianPts:uim and its family of of packages
 * DebianPts:fcitx and its family of of packages
 * DebianPts:scim and its family of of packages
 * DebianPts:ibus and its family of packages
 * DebianPts:uim and its family of packages
 * DebianPts:fcitx and its family of packages
 * DebianPts:scim and its family of packages
Line 41: Line 41:
 * communicate publically on this ML or BTS of packages. (Along with the social contract #3: "We will not hide problems")
 * use alioth VCS (mainly git with '''git-buildpackge''' style '''master''' + '''upstream''' + '''pristine-tar''' branches) archive with '''collab-maint''', if possible. (Not to use package or group specific section of VCS system to ease migration between maintainers.)
 * communicate publicly on this ML or BTS of packages. (Along with the social contract #3: "We will not hide problems")
 * Respect and follow the guidelines and best practices

== guidelines ==

 * pkg-ime
  * use pkg-ime-devel@lists.alioth.debian.org to communicate
  * use alioth VCS service under '''collab-maint''' group, if possible. (Do not to use package or group specific section of VCS system to ease migration between maintainers.)
  * use '''git''' with '''git-buildpackge''' style archive organization, if possible. ( '''master''' + '''upstream''' + '''pristine-tar''' branches)
 * ibus
  * plugin-executables: place them under /usr/lib/ for wheezy
  * compat=9
Line 55: Line 65:
Developer status:

  * senior: active participation in jessie cycle expressed
  * junior: no response

IME Packaging Team

Infrastructure

Interacting with the team

Usual roles

Task description

Work and coordinate to provide the good Input_method infrastructure to the Debian desktop.

Typical candidates packages are:

  • im-config (and its predecessor im-switch)

  • ibus and its family of packages

  • uim and its family of packages

  • fcitx and its family of packages

  • scim and its family of packages

Member requirements

The requirements to the members are the following (This is based on the de facto practice and only an tentative one.):

  • interested in maintaining the good IME packages on Debian. (No need to have packages)
  • abide by the Debian Social Contract.

  • willing to work with other people on the IME packaging team.
  • communicate publicly on this ML or BTS of packages. (Along with the social contract #3: "We will not hide problems")
  • Respect and follow the guidelines and best practices

guidelines

  • pkg-ime
    • use pkg-ime-devel@lists.alioth.debian.org to communicate

    • use alioth VCS service under collab-maint group, if possible. (Do not to use package or group specific section of VCS system to ease migration between maintainers.)

    • use git with git-buildpackge style archive organization, if possible. ( master + upstream + pristine-tar branches)

  • ibus
    • plugin-executables: place them under /usr/lib/ for wheezy
    • compat=9

Get involved

If you wish to join, please get alioth.debian.org account and request via its web interface at alioth and also send your message to the mailing list.

How-to's on collab-maint join requests on Alioth:

Developer status:

  • senior: active participation in jessie cycle expressed
  • junior: no response

More stuff

TBA