Differences between revisions 1 and 9 (spanning 8 versions)
Revision 1 as of 2013-06-04 13:45:30
Size: 2301
Editor: OsamuAoki
Comment:
Revision 9 as of 2014-05-04 05:17:35
Size: 3560
Editor: OsamuAoki
Comment:
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
 * DebianPts:im-config Typical candidates packages are:
Line 28: Line 28:
== Get involved ==  * DebianPts:im-config (and its predecessor DebianPts:im-switch)
 * DebianPts:ibus and its family of packages: See [[Teams/IMEPackagingTeam/ibus|pkg-ime: ibus status]]
 * DebianPts:uim and its family of packages
 * DebianPts:fcitx and its family of packages
 * DebianPts:scim and its family of packages

== Member requirements ==
Line 35: 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
Line 38: Line 44:
== More stuff == == 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)
 * packaging style
  * "dh $@" style (dh7) preferred in debian/rules
  * multi-arch support as much as possible.
  * compat=9
  * plugin-executables location coordination:
    * For ibus-family packages, multi-arch-forein plugin-executables needs to override default with LIBEXECDIR=/usr/lib/ibus/ (please note there is no arch name)
== Get involved ==
Line 43: Line 65:
  * http://wiki.debian.org/Alioth (general guide for alioth system)
  * https://alioth.debian.org/projects/pkg-ime/ (click near the right bottom corner)
 * http://wiki.debian.org/Alioth (general guide for alioth system)
 * https://alioth.debian.org/projects/pkg-ime/ (click near the right bottom corner)
Line 48: Line 70:

Developer status:

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


== More stuff ==

TBA

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:

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)

  • packaging style
    • "dh $@" style (dh7) preferred in debian/rules
    • multi-arch support as much as possible.
    • compat=9
    • plugin-executables location coordination:
      • For ibus-family packages, multi-arch-forein plugin-executables needs to override default with LIBEXECDIR=/usr/lib/ibus/ (please note there is no arch name)

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