[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Possibility of moving package fcitx-imlist under Debian Input Method Team



2018-02-17 18:40 GMT+08:00 Kentaro Hayashi <kenhys@gmail.com>:
> Hi,
>
>
> 2018-02-08 19:07 GMT+09:00 Boyuan Yang <073plan@gmail.com>:
>>
>> 2018-02-06 10:38 GMT+08:00 Kentaro Hayashi <kenhys@gmail.com>:
>> > Hi,
>> >
>> >> In order to make the maintenance of input-method-related packages
>> >> easier
>> >> and
>> >> more unified, could you please consider putting the package under team
>> >> maintenance
>> >> from Debian Input Method Team? Team members can also provide with
>> >> package
>> >> upload sponsorship if you think it necessary.
>> >
>> >
>> > It's a tiny software and not well-known, not widely used one, but it's a
>> > good idea to maintain by
>> > team.
>> > As a migration task, what should I do next for team maintainance?
>>
>> Currently the fcitx 4.2.9.5 transition is not a blocker (the package
>> is binNMU-ed already [1]).
>>
>> To complete the migration, you may prepare a new version and get it
>> uploaded, in which
>> the maintainer / uploaders fields are updated. Other changes and fixes
>> are encouraged
>> to get included too (such as lintian warning fixes, packaging standard
>> upgrades or
>> patches from upstream trunk).
>>
>> Regards,
>> Boyuan Yang
>>
>> [1] https://wiki.debian.org/binNMU
>
>
>
> FYI:
> I've filed new version as RFS: 0.5.1-2, which updates Maintainer: field to
> Debian Input Method Team.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890648
>
> Then I'll consider to migrate fcitx-imlist package repository to salsa.d.o.
> As for Debian Input Method Team, it should be
> https://salsa.debian.org/debian/fcitx-imlist
> or put under Team repository (I can't find it)?
>
> --
> Kentaro Hayashi <kenhys@gmail.com>

Thanks for that work!

There's no separate team (group) on Salsa for this team; we are
putting everything
under the big Debian group. Any DD has the permission to create a repo there.

--
Regards,
Boyuan Yang


Reply to: