Gentoo Archives: gentoo-dev

From: Mikael Hallendal <hallski@g.o>
To: "Gentoo Dev." <gentoo-dev@××××××××××.org>
Subject: Re: [gentoo-dev] What should be in place before 1.0 release
Date: Mon, 15 Oct 2001 06:04:54
Message-Id: 1003147453.14313.54.camel@fry
In Reply to: Re: [gentoo-dev] What should be in place before 1.0 release by Blue Lizard
1 mån 2001-10-15 klockan 11.35 skrev Blue Lizard:
2
3 > Well, if you are making a new interface to bugzilla (or whatever backend
4 > is chosen), which seems preferable, then it is not a big deal to have
5 > separate interfaces (like different forms on a website) for a BR, UC, or
6 > FER. Bug report, usability correction, and feature enhancement request
7 > respectively. That way if someone not very intigrated with development
8 > or clueless about code thinks 'it would be cool if you could...' he need
9 > say little more. And it would be easier for triage, version control,
10 > that kind of thing. That is, easier from the POV of the person writing
11 > the report/request and easier for the developer(s) it concerns. So yes,
12 > I agree that writing a gentoo interface is a good idea. Roundup is
13 > pretty, but I fear that it might not suit our purposes very well.
14 > Still, learn from it. While implementing our own interfaces (kinda like
15 > real time triage), take from it that ease of gathering together all your
16 > active 'stuff' together. Page for users to look at bugs they've filed
17 > and their status, activity, etc. (think MyPage on ubid). Page for
18 > developers to see bugs assigned to them, if they are qa contact, if a
19 > bug has patch up for review and it falls in their 'sector'
20 > (component/area), new bugs that would be of interest (falls in area of
21 > specialty, contact, someone cc'ed them, etc.). Note that unlike
22 > mozilla's implementation, it is more contained in one system unit
23 > thingy. Like instead of being based on emails and cc's and chechking
24 > boxes or filling in...this is all totally together in my head but to put
25 > into words or code seems impossible. Think like the way it sorta
26 > (great, now the idea is evolving too far beyond the example) ... ya
27 > know. Like the way MandrakeExpert sorta kinda doesn't really work.
28 > Replace the expert select check boxes with a pulldown menu that updates
29 > with the selection of component and other aspect triaging attributes
30 > that minimize the required user knowledge background. This is so
31 > incoherent I'm just gonna stop. Look at this, not a single line break.
32 > It's how I think, must be why I'm always so confused ;P
33
34 Yes, but next time, PLEASE use linebreaks and it will be easier to read
35 the mail.
36
37 Regards,
38 Mikael Hallendal
39
40 --
41
42 Mikael Hallendal
43 Gentoo Linux Developer, Desktop Team Leader
44 CodeFactory AB, Stockholm, Sweden