[arch-dev-public] bugtracker vs package cleanup

[Roman Kyrylych]

2007/5/13, Jason Chu <jason at archlinux.org>:
> On Sun, May 13, 2007 at 01:21:27PM +0300, Roman Kyrylych wrote:
> > 2007/5/13, Aaron Griffin <aaronmgriffin at gmail.com>:
> > > On 5/12/07, eliott <eliott at cactuswax.net> wrote:
> > > > > "Dan McGee" <dpmcgee at gmail.com> wrote:
> > > > > I've never liked AUR comments as a method of tracking bugs. Using a
> > > > > bug tracker seems like the right way to do things, and I don't think
> > > > > it would be too big of a problem to either refine the AUR project that
> > > > > already exists or start a new one.
> > > >
> > > > I agree with Dan.
> > > >
> > > > Further, I think that since it largely seems that the TUs have historically
> > > > been the pool from which several devs were brought in from, that it makes
> > > > sense to have those folks using many of the same tools. This has a dual
> > > > benefit of reducing the tools that are used (focusing), and getting potential
> > > > new devs more familiar with the existing tools (training).
> > >
> > > Another benefit is making the TUs seem less like "second class
> > > citizens" as someone else said.  TUs are critical to Arch in it's
> > > current state.
> >
> > So, if noone complaints and everyone think that's a good idea - please
> > setup Flyspray for this. ;-)
> > There are few possibilities:
> > 1) new project
> > 2) new group in AUR project
> > 3) new group in Arch Linux project
> >
> > 3rd seems more logical, IMHO.
>
> What will the comments for AUR packages become then?  Aren't they just used
> for problems and for users congratulating people?
>
> When we first wrote the system, the reason we wanted people to be able to
> post comments and not use a bug tracker was so that anyone looking at the
> package in the AUR interface would also see all the problems that people
> had brought up.  With a bug tracker, that won't be possible anymore...

Hm, but then why don't we have such system for official packages?

I think bugtracker is better when there are more than one open issue
for given package.
On the other hand, easily accessible list of all current issues is good.
So why not extend website to include links to all open flyspray's
bugreports regarding given package?

-- 
Roman Kyrylych (Роман Кирилич)