I shortly discussed this with Martin last night on IRC:
<dpm> pitti, is it possible to have an apport hook for a project in LP, even if there isn't a source package available? We are using the ubuntu-translations project to track translation bugs, and I was thinking if it would be possible to have something like 'ubuntu-bug translations' and file a bug against ubuntu-translations
<pitti> dpm: yes, we could arrange that; it sounds like a good symptom to have
<pitti> dpm: a symptom script is not related to a package; however, right now it has to figure out an affected package name
<pitti> dpm: but this could just be language-pack-$LANG, and the symptom code could instruct Apport to file the bug against a project instead
So, in short, the suggestion is to use an apport symptom, get the reporter to run 'ubuntu-bug language-pack-$LANG' (where $LANG is his/her language code), and the symptom would file the bug against the ubuntu-translations project.
The only problem I can see with this approach is that most users do not know about language codes, so it might be difficult to instruct people to run 'ubuntu-bug language-pack-ca' if they have to figure out the language code. 'ubuntu-bug translations' would be much easier, but it's not doable because we haven't got a 'translations' source package. Is there any other easier-to-figure-out source package related to translations we could use for that?
I shortly discussed this with Martin last night on IRC:
<dpm> pitti, is it possible to have an apport hook for a project in LP, even if there isn't a source package available? We are using the ubuntu-translations project to track translation bugs, and I was thinking if it would be possible to have something like 'ubuntu-bug translations' and file a bug against ubuntu-translations pack-$LANG, and the symptom code could instruct Apport to file the bug against a project instead
<pitti> dpm: yes, we could arrange that; it sounds like a good symptom to have
<pitti> dpm: a symptom script is not related to a package; however, right now it has to figure out an affected package name
<pitti> dpm: but this could just be language-
So, in short, the suggestion is to use an apport symptom, get the reporter to run 'ubuntu-bug language- pack-$LANG' (where $LANG is his/her language code), and the symptom would file the bug against the ubuntu-translations project.
The only problem I can see with this approach is that most users do not know about language codes, so it might be difficult to instruct people to run 'ubuntu-bug language-pack-ca' if they have to figure out the language code. 'ubuntu-bug translations' would be much easier, but it's not doable because we haven't got a 'translations' source package. Is there any other easier- to-figure- out source package related to translations we could use for that?