Because many packages will be moved to Community I'd like to point few things regarding our bugtracker: 1) there is some amount of open bugreports for packages that are moving to Community/Unsupported. 2) there will be more packages in Community which means there will be larger amount of bugs in them (summarized). Maybe it's a time now to create a new project in Flyspray for Community packages, and give all TUs permissions to assign/edit/close bugs in that project? Besides of a bit better tracking of bugs in Community packages this will allow to move those open bugreports for Community packages to new Flyspray's project. Or should Community packages continue to use AUR comments for reporting and discussing bugs? Opinions? -- Roman Kyrylych (Роман Кирилич)