Differences between revisions 1 and 11 (spanning 10 versions)
Revision 1 as of 2013-06-04 13:45:30
Size: 2301
Editor: OsamuAoki
Comment:
Revision 11 as of 2019-03-31 12:01:43
Size: 4265
Editor: OsamuAoki
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * '''Website''': http://qa.debian.org/developer.php?login=pkg-ime-devel@lists.alioth.debian.org
 * '''Alioth Project''': http://alioth.debian.org/projects/pkg-ime
 * '''Documentation''': [[http://lists.alio
th.debian.org/pipermail/pkg-ime-devel/2013-June/002985.html|See call for help as a starter]]
 * '''Unix group''': pkg-ime (help to s
et up web page appreciated)
 * '''Debian QA Website''': https://qa.debian.org/developer.php?login=debian-input-method@lists.debian.org
 * '''Salsa Project''': https://salsa.debian.org/input-method-team/ Debian Input Method Team
Line 13: Line 11:
 * '''Email contact''': pkg-ime-devel@lists.alioth.debian.org
 * '''Email archive''': https://alioth.debian.org/mail/?group_id=30337
 * '''Request tracker''': Please use Debian BTS for each package
 * '''Email contact''': Debian Input Method Team <debian-input-method@lists.debian.org>
 * '''Email archive''': https://lists.debian.org/debian-input-method/
 * '''Request tracker''': Please use Debian BTS for each package for now
Line 20: Line 18:
 * See [[http://alioth.debian.org/project/memberlist.php?group_id=30337|Project Member List]]  * See [[https://salsa.debian.org/groups/input-method-team/-/group_members|Project Member List]]
Line 26: Line 24:
 * DebianPts:im-config Typical candidates packages are:
Line 28: Line 26:
== 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 39:
 * 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

== Member guidelines ==

 * packaging activities
  * use '''utils''' package section for the IME main package and its plug-in packages.
   * (Do not use '''misc'''.)
  * subscribe to debian-input-method@lists.debian.org to be reachable (main communication channel)
  * use the salsa service to create a Git repository to host your packaging activity under one of the following sites:
    * https://salsa.debian.org/debian (Debian group write accessible by all DD)
      * If this is used, add "Debian Input Method Team"(input-method-team) to each project repository via its side panel: Settings -> Members -> "Share with Group" tab.
    * https://salsa.debian.org/input-method-team (Debian Input Method Team site write accessible by all Debian Input Method Team member)
      * If this is used, add "Debian"(debian) to each project repository via its side panel: Settings -> Members -> "Share with Group" tab.
      * In future, the whole projects belonging to this team will be set write accessible by all DD.
  * use '''git''' with '''gbp-buildpackge''' style archive organization, if possible. ( '''master''' + '''upstream''' + '''pristine-tar''' branches)
    * If branch name choices are different, add '''debian/gbp.conf''' file to the package.
    * If possible, use '''pristine-tar'''
  * respect contributors who make high quality serious packaging activity.
    * If you only update packages by using '''uscan''' mechanism and applying contributed patches, you should ask such a contributor to lead the maintenance. (I know it is hard to find such a contributor.)
 * packaging style
  * '''dh $@''' style (post-dh7) must be used in debian/rules
  * multi-arch support as much as possible.
  * compat=11
  * plugin-executable location coordination:
    * For ibus-family packages, multi-arch-forein plugin-executable programs need to override the default with '''LIBEXECDIR=/usr/lib/ibus/''' (please note there is no arch name)

== Get involved ==

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

 * https://wiki.debian.org/Salsa (general guide for salsa system)
 * https://salsa.debian.org/input-method-team (click "Request Access" button in the top section of the page)

Developer status:

 * "Maintainer" for active member (last 2 years)
Line 40: Line 81:
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.
 * InputMethodBuster
Line 43: Line 83:
  * http://wiki.debian.org/Alioth (general guide for alioth system)
  * https://alioth.debian.org/projects/pkg-ime/ (click near the right bottom corner)

How-to's on collab-maint join requests on Alioth:
 * https://lists.debian.org/debian-devel-announce/2012/01/msg00006.html
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

Member guidelines

  • packaging activities
    • use utils package section for the IME main package and its plug-in packages.

      • (Do not use misc.)

    • subscribe to debian-input-method@lists.debian.org to be reachable (main communication channel)

    • use the salsa service to create a Git repository to host your packaging activity under one of the following sites:
      • https://salsa.debian.org/debian (Debian group write accessible by all DD)

        • If this is used, add "Debian Input Method Team"(input-method-team) to each project repository via its side panel: Settings -> Members -> "Share with Group" tab.

      • https://salsa.debian.org/input-method-team (Debian Input Method Team site write accessible by all Debian Input Method Team member)

        • If this is used, add "Debian"(debian) to each project repository via its side panel: Settings -> Members -> "Share with Group" tab.

        • In future, the whole projects belonging to this team will be set write accessible by all DD.
    • use git with gbp-buildpackge style archive organization, if possible. ( master + upstream + pristine-tar branches)

      • If branch name choices are different, add debian/gbp.conf file to the package.

      • If possible, use pristine-tar

    • respect contributors who make high quality serious packaging activity.
      • If you only update packages by using uscan mechanism and applying contributed patches, you should ask such a contributor to lead the maintenance. (I know it is hard to find such a contributor.)

  • packaging style
    • dh $@ style (post-dh7) must be used in debian/rules

    • multi-arch support as much as possible.
    • compat=11
    • plugin-executable location coordination:
      • For ibus-family packages, multi-arch-forein plugin-executable programs need to override the default with LIBEXECDIR=/usr/lib/ibus/ (please note there is no arch name)

Get involved

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

Developer status:

  • "Maintainer" for active member (last 2 years)

More stuff

TBA