So if I understood right. One good step to help is (for example) to create a
documentation on how to create and submit a patch in order for those that
want to help (and know how to code) but don't know what, where and when they
must send the changes to do it easily ?
I think that the problem here (and I can be wrong) is not about you (as the
team) don't listening to us but more we (the community) not knowing what is
really needed in emergency for this project. As an example, I'm pretty sure
that if someone from "the top" said something like : "Package XYZ has a bug
that I don't have time to solve could anyone do this" then this bug will be
mostly corrected in the same day.
I am saying this because, I am working right know on a small team of people
that have they own daily jobs (that are, by this reason, more important than
the project we are doing) and the organization is a bit messy because of
this. Because they are a bunch of good people trying to help us but we just
can't provide them the resources to do so, simply because if we could then
this time spent would be spent on doing the project itself.
But once again, maybe I'm seeing this wrong. Personally I have problems with
DEB packages, I am trying to learn but I still can't find a good way to do
this after reading a lot of documentation (this is why I criticize the debian
packaging over the arch linux packaging). It is like the snap window problem
on Compiz. I have an idea on how to solve it (I already tried out when Ubuntu
12.04 came out. At that time I didn't even know about trisquel). But I just
don't know how to compile only the compiz plugins since I don't find any
information about it anywhere.
And I'm pretty sure that I'm not the only one on this situation.
