In case our flyspray admins don't read tur-users ML frequently. ---------- Forwarded message ---------- From: Roman Kyrylych Date: 1 Лис 2007 20:25 Subject: Re: [tur-users] [arch-dev-public] flyspray category for supp./unsupp. community packages? To: "Discussion about the Arch User Repository (AUR)" 2007/10/25, Roman Kyrylych :

2007/10/25, Thomas Bächler :

...

Roman Kyrylych schrieb:

...

See http://archlinux.org/pipermail/arch-dev-public/2007-May/000718.html Could we setup Flyspray so all community packages will reside in "Packages: Community" category? My concern is privilege separation between different categories of the same project.

What about creating a separate project? ArchLinux and Community are in a sense separate projects, so we could simply add a new one (with a good name, we already have an AUR project).

As long as we can move bugs between projects (can we?), this shouldn't be a problem. It may confuse users though.

Yes, the only problem with separate project is user confusion. We are receiving ~10 reports per week in wrong project now, because Flyspray remembers active project in a cookie.

But it seems that we cannot do any privilege separation in one project, so separate project appears to be the only good variant.

Could our Flyspray admins give me the "Project Manager" status on Community packages?

ping There are already 2 bugreports in "Community Packages" project (one of which should be assigned to me) but I cannot do anything with them. Just give me the Project Manager status and then I'll setup everything else. -- Roman Kyrylych (Роман Кирилич)