1 |
Ok, |
2 |
|
3 |
First off, I agree calling it issuetracker is a better idea than |
4 |
bugtracker, because of the desire to handle ebuilds/feature |
5 |
requests/etc. Also, I definately agree, an easy to use interface is very |
6 |
important. That's mainly why I don't like bugzilla very much. |
7 |
|
8 |
I think PEST would be the best system to use, I just came across it |
9 |
yesterday when searching for bug tracking software. The reasons I |
10 |
think its a good option are: |
11 |
|
12 |
- Good looking, simple interface, should be easy to use |
13 |
- Has advanced features so project members should be able to do what |
14 |
they need. |
15 |
- Written in PHP so its easy to modify |
16 |
- Under active development and seems to have a decent sized community, |
17 |
so its probably not going to go anywhere. |
18 |
|
19 |
So if Thread and chadh would like to contact me about letting me set |
20 |
something up, that would be cool. If anyone has any |
21 |
suggestions/comments, let me know. I think I will start in the mean time |
22 |
by setting up a test installation on my own server to see how hard it is |
23 |
to install and see what the issues are. |
24 |
|
25 |
-Josh |
26 |
|
27 |
|
28 |
On Wed, Nov 28, 2001 at 04:21:58PM +0100, Karl Trygve Kalleberg wrote: |
29 |
> On Tue, 27 Nov 2001 11:22:04 -0500 |
30 |
> Joshua Pollak <pardsbane@××××××××××.org> wrote: |
31 |
> |
32 |
> > Something along the lines of Bugzilla/SF's features/phpBugTracker, etc, |
33 |
> > should be fine, right? I could set it up on my own server, or I can set |
34 |
> > it up somewhere else. If the project is willing to accept the work, once |
35 |
> > done, I'll get started right away. |
36 |
> |
37 |
> See if you can't get in contact with chadh on how to set it up on |
38 |
> cvs.gentoo.org (which perhaps should get a new alias: bugs.gentoo.org ?). |
39 |
> |
40 |
> We should have at least two modes for the bugtracker: end-user and |
41 |
> developer. The full-blown bugzilla interface is a bit intimidating for |
42 |
> first-time end-users, so they should by default get an easy-to-use |
43 |
> interface. |
44 |
> |
45 |
> The regular developers should get the full-blown interface, I guess. |
46 |
> |
47 |
> The main thing about the bugtracker is that we should _USE_ it. So we'll |
48 |
> just have to keep tweaking it until everybody uses it for adding ebuilds, |
49 |
> bug reports, wishes, etc. |
50 |
> |
51 |
> In fact, we should perhaps rename it from "bugtracker" to "issuetracker", |
52 |
> since we want to have it handle more than just bugs: we want all new |
53 |
> ebuilds to be submitted through it, so that it can help us not forget half |
54 |
> of the ebuilds that get submitted. |
55 |
> |
56 |
> Karl T |
57 |
> _______________________________________________ |
58 |
> gentoo-dev mailing list |
59 |
> gentoo-dev@g.o |
60 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |