Re: [Tails-project] Fwd: Ticket #17703 (Direct volunteers to…

intrigeri:
>> Ok, so the information mapping that we are missing is which projects do
>> we have in which programming language, right?
>
> Yes, that's the most important criterion I can think of, for code stuff.

So I created #10708 about that.

> There may be other missing mappings for other types of work, if anyone
> wanted to do something like Mozilla's.
> E.g. Puppet or not, for sysadmin.
> Upstream or Tails-specific, for lots of stuff.
> Desktop or web, for UX design.
> Etc.
>
> But if someone fixes the most important issue for code tasks, in
> a maintainable way, even if it's not a fancy and generic solution,
> I'm happy :)

I wonder about the "maintainable" side of this. This mapping would be
only (or mostly) useful if it leads people to lists of Redmine tickets
for example (or lists of people to talk to). So if it's somehow
implemented in ikiwiki (either as a static page or a fancy webapp), then
we need some mapping to point to Redmine tickets.

Maybe the articulation between the two could be the "Affected tool"
field. It's a bit simplistic, but if you know Python you are likely to
be helpful on the Greeter, if you know Perl likely to be helpful on the
Upgrader.

Maybe we need a few more "Affected tool" to have a better coverage
between pieces of code and Redmine tickets (for example, maybe we need
an affected tool for "Puppet modules"). Then each of them could be
listed with their programming languages on /contribute/easy_tasks.

Also, maybe we could be better at gardening the easy tasks (make sure we
have some and that they are well described). For example, I reckon that
I spend very little time on this myself.