2301
Comment:
|
3260
|
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 * 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) * ibus packaging * plugin-executables: place them under /usr/lib/ for wheezy * compat=9 == Get involved == |
Line 43: | Line 63: |
* 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 68: |
Developer status: * senior: active participation in jessie cycle expressed * junior: no response == More stuff == TBA |
IME Packaging Team
Infrastructure
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: See call for help as a starter
Unix group: pkg-ime (help to set up web page appreciated)
Interacting with the team
Read the FAQ first: not yet implimented
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
Public IRC channel: Not-used at this moment
Usual roles
Task description
Work and coordinate to provide the good Input_method infrastructure to the Debian desktop.
Typical candidates packages are:
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.
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:
Developer status:
- senior: active participation in jessie cycle expressed
- junior: no response
More stuff
TBA