[Trisquel-devel] Bugs that could use closing / won't fix

[Grant H.]

I have kinda started to dive into some of the Trisquel issues.  I have
found some issues which I think can be closed as status "fixed" or
"won't fix".  I don't have the rights to do that to bugs though.  I
based my criteria off of the community driven tasks section of this page
(https://trisquel.info/en/wiki/how-help) on the kinds of requests we
can't accept.  Those are the ones on the left hand column.  The ones in
the right are ones for whatever reason (see key) may be only relevant to
an old non-supported version of trisquel, fixed by upstream, or already
fixed but the bug was never closed ect.

These are just my opinions/recommendations on these bugs.  Please see
the attached spreadsheet.
-- 
*Grant H.
*Email: ghoulgat at member.fsf.org
*Ask me for my GPG key
*I'm an FSF member -- Help us support software freedom!
<http://www.fsf.org/jf?referrer=8999>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Bugs.ods
Type: application/vnd.oasis.opendocument.spreadsheet
Size: 13456 bytes
Desc: not available
URL: <http://listas.trisquel.info/pipermail/trisquel-devel/attachments/20120125/c8e256f0/attachment-0001.ods>