Autor: sajolida Data: Para: The Tails public development discussion list Asunto: Re: [Tails-dev] Redmine: possible usage clarification and
improvements
intrigeri wrote: >> - Camouflage
>
> Hrm, no, Camouflage is a category IMO. We've had camouflage issues
> affect the browser, the OpenPGP applet, etc.
Ok.
>> [...]
>> - Incremental upgrades
>
> Then it should be renamed to "Upgrader", I think. And maybe some day
> we'll need an "Incremental upgrades" category.
XXX
>> [...]
>> - Spoof MAC
>
> "Spoof MAC" looks like a category to me too. We don't really have one
> central tool that implements it. But I'm not sure.
It has only 6 tickets so it's no big deal I think.
>> Not sure:
>
>> - Installation: it used to be called "Installer" but I renamed it to be
>> able to put there documentation issues related to installation.
>
> I think we need a "Tails Installer" tool, and probably also an
> "Installation" category where you can put stuff that warranted the
> generalization you did previously.
I thought about that too so it must be a good idea.
>> - Tor configuration: "category"?
>
> I think we should probably have a "Tor configuration" category, and
> a "Tor launcher" affected tool.
Ok.
>> - FAQ: should this be a "tool"?
>
> I can think of cases when we want to specify what tool a FAQ-related
> ticket is about, and cases when we want to specify which category it
> is about. The FAQ thing really doesn't fit well into this taxonomy, no
> big surprise considering it's really something totally transversal.
> Let's try either one, and see..
Ok.
>> - Mirrors: "tool"?
>
> I think we could set category = Infrastructure for all tickets that
> currently have category = Mirrors: it's really a sub-category.
> And then, we'll want a check-mirrors "Tool". Only two of these tickets
> (#7161, #7125) will be left without an "Affected tool" field, and
> they're really about general infrastructure things, that don't really
> need to be classified more precisely IMO.
Ok.
>> - Build system: "tool"?
>
> I've had a look at the corresponding tickets, and I would put it as
> a category, so that we can have tool = {Vagrant, Docker, live-build,
> you-name-it}.
