Bug#823521: RFS: irstlm/6.00.05-1 -- IRST Language Modeling Toolkit
On 06/05/16 09:30, Giulio Paci wrote:
Il 06/mag/2016 08:36, "Ghislain Vaillant" <ghisvail@gmail.com
<mailto:ghisvail@gmail.com>> ha scritto:
> 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.
Good.
> Then, you can move the packaging repository over, change the
Maintainer field to "Debian Science Maintainers <debian-science-
> maintainers@lists.alioth.debian.org
<mailto: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.
You are supposed to checkout the repository with:
git+ssh://git.debian.org/git/blends/projects/science.git
Edit the relevant task files, commit and push. The sentinels will
be refreshed accordingly on the next job.
>
>
> 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?
Indeed.
> 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.
Linguistics sounds the most appropriate. I'd say machine-learning and
statistics should rather be for more generic packages, since any piece
of software which is a minimum applied (such as this one) is expected to
use a mixture of those.
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.
It would be a nice gesture towards upstream.
Cheers,
Ghis
Reply to: