Am 18.08.2014 um 10:01 schrieb mrlemux@gmail.com:
the problem is that most issue tracking systems are too heavy for our uses(correct me if i'm wrong), and if we want it really KISS we have to implent an issue tracking system ourselves (with a feature base like github's one). i think it could replace the current comment section as it is mostly used for reporting Bugs already
I also like this idea. Over the years the package pages have been cluttered with comments that are not applicable today anymore. Who cares today, if a version from 2007 did not compile correctly? Also users tend to write a small comment "version x.y is out" when flagging a package out of date and leave it there after the package has been updated. It would be nice to have a lightweight tracker, that allows the user to choose between at least 3 types of ticket: bug, comment, out-of-date. The maintainer can then close an out-of-date ticket with a git push or respond to a bug report. Comments that are not not relevant anymore can also be closed after a time. If we think this a bit further, also the request system can be integrated as tickets that can be only closed by a TU. This would also avoid the cluttering we have today with the additional mailing list, as closed tickets can be shown when needed later. I think everything should be a "bug",and TU's and maintainers should both have the same rights(the right to merge commits(But there are rules they have to follow)), users could associate commits by commiting there files with a special tag that referes to that "bug"(something like {fix:#<issue_number>})
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/19/2014 11:18 AM, carstene1ns wrote: these would then also appear in the current "thread" The bug could then, be either closed by merging the commit with the assoxiated {fix:#} (Users have 5 Days time to reopen the bug if it just fixes half of it or something like that) or have a specialcommit which refers to the bug in the commit message(something like {close:#<issue_number>}, or a designated close button -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJT8y+gAAoJEBWTDgtqAPQNwakIAL1LqjjG9olQTIxYenygbqlL x8Ww2nHxz4dnYo3eE5QAJDwSqJ96fUJHltqZ+OLZ6tjM2KPsqGJ0bw7Fla9n5Dgo 9hdgg6YDIZAQJ8IesDRCiE6HQBf2plJ7BMqqA8pJCRYW7KGYc22JTkMs6kQryuWG 95HreC1keixXMbew4Udb3ECDquCUsCKEzw5Q6dHlgQPVlVRMZ4XqrJ92n3eOlII+ EBlriPSAWtYgAyb9R6MrLycsuLOT0A+gOE5CaU5UbVaDPiVL2ev9qsKARJ1uypTA iT2lQNZkRSrQ8C63VRx+8lN4zUI7SFZfOktoawh2sE2F6wkzgdCt5JeLJs+WruA= =1geE -----END PGP SIGNATURE-----