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

Bug#823521: RFS: irstlm/6.00.05-1 -- IRST Language Modeling Toolkit



Il 06/mag/2016 08:36, "Ghislain Vaillant" <ghisvail@gmail.com> ha scritto:
>
> On 06/05/16 02:48, Giulio Paci wrote:
>>
>> On 05/05/2016 19:45, Ghislain Vaillant wrote:
>>>
>>> On 05/05/16 17:16, Giulio Paci wrote:
>>>>
>>>> Package: sponsorship-requests
>>>> Severity: normal
>>>> X-Debbugs-CC: rbalint@debian.org
>>>>
>>>> Dear Balint,
>>>>
>>>> I am looking for a sponsor for an updated version of my package "irstlm"
>>>>
>>>>    * Package name    : irstlm
>>>>      Version         : 6.00.05-1
>>>>      Upstream Author : Marcello Federico <federico@fbk.eu>
>>>>    * URL             : https://github.com/irstlm-team/irstlm/
>>>>    * License         : LGPL-2.1
>>>>      Programming Lang: C++, Perl, Bash
>>>>      Description     : IRST Language Modeling Toolkit
>>>>      Section         : misc
>>>>
>>>> This package includes latest upstream releases and several package updates.
>>>>
>>>> You can found the sources for the package and additional information at:
>>>>
>>>>     https://anonscm.debian.org/cgit/collab-maint/irstlm.git/
>>>>
>>>> A review of the package is more than welcome.
>>>>
>>>> Regards,
>>>>      Giulio Paci
>>>>
>>>
>>> Hi Giulio,
>>>
>>> You might be interested to move this package to co-maintenance under the
>>> Debian Science Team [1] and integrate it to one of the tasks [2] in the
>>> future (perhaps the linguistics task [3]?).
>>
>>
>> You are right, and it is my intention to do so in future.
>> The only thing stopping me is that at the moment the sponsorhip for this package is working and I have very scarce time, so that I had not yet reread the rules of the team
>> (last time I read them was a few years ago).
>
>
> It is not that much overhead actually.

You are probably right, but still I think it would be nice to know the team policy and workflows before the change.

> You just need to join the team
> on alioth, which will grant you access to the team's git repositories.

If I remember correctly I am already part of the team, although I never contributed to package maintainance.
The wiki page of the team also report me as a team member.

> Then, you can move the packaging repository over, change the Maintainer field to "Debian Science Maintainers <debian-science-
> maintainers@lists.alioth.debian.org>" and move yourself to the
> Uploaders field.

>> Regarding the tasks, I think "linguistics" is fine. In addition, what about "machine learning" and/or "statistics"?
>>
>> How can I add them to the tasks? I have found this repository https://anonscm.debian.org/cgit/blends/projects/science.git but no clear instructions.
>
>
> This process is actually independent of having the package maintained
> under the DST or not. However, you need to join the team to be able to
> modify the task files.

Are the task files the only files that needs to be changed? Am I expected to make the changes directly on the repository?

> I can add the package to linguistics, machine
> learning and statistics.

What I meant with my question is: are those two tasks right for this package? They are surely strongly related, probably more than linguistics, but, I do not know if the intended users of these tasks may expect to find this package on their system. Are there a description of the tasks which includes some use case description (or use case description that includes tasks suggestion)? If not, probably it would be nice to have some use case description somewhere that my help users to better understand if the task is useful for them or not and may further help us in deciding if a package is suitable for a given task.

Anyway, if you can add the package to relevant tasks, I will try to learn by example how to do that. ;-)

> You might want to add some upstream metadata [1], so our sentinels can
> display additional information about the software such as screenshots,
> citations...
> [1] https://wiki.debian.org/UpstreamMetadata

I will read the page during the next few days. I think citations is important for upstream of these packages.

> Thanks for working on this package.

Thank you for your suggestions.

Giulio


Reply to: