Differences between revisions 5 and 6
Revision 5 as of 2013-06-13 12:52:20
Size: 3138
Editor: OsamuAoki
Comment:
Revision 6 as of 2013-09-13 15:44:52
Size: 3260
Editor: OsamuAoki
Comment:
Deletions are marked like this. Additions are marked like this.
Line 50: Line 50:
  * 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 alioth VCS service under '''collab-maint''' group, if possible.
    *
Do not to use package or group specific section of VCS system to make it easy for other DDs to contribute.
    * We still use '''pkg-ime''' group for many existing packages for historic reason. (This is acceptable
.)

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 activities
    • use utils package section for the IME main package and its plug-in packages.

      • (Do not use misc.)

    • 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 make it easy for other DDs to contribute.
      • We still use pkg-ime group for many existing packages for historic reason. (This is acceptable.)

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

  • ibus packaging
    • 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