Jeremy Huntwork wrote:
DJ Lucas wrote:
The very first (and most annoying) thing I've noticed (that will affect
me) is that the default when clicking on a file in the source browser is
the current revision instead of revision history. That will just drive
me batty!
Heh, that's funny. I felt the opposite - I'm glad to see the file right
away. I wonder how many feel the way you do on this one?
Well from a book development standpoint, I already have the latest and
greatest in my local copy. Just to show you where I'm coming from,
usually when I look at viewcvs, I'm looking for a specific change, as I
would supspect others are. Wether it's in (*)lfs book sources, or the
cvs/svn repo for a package that is having difficulty with the latest
gcc, jdk, bdb, samba, etc. really doesn't matter, I'm still usually
looking for a specific change. I kinda figure that is why most people
would look to viewcvs...or maybe I am just the oddball. :-)
Furthur, the default view in every webviewer of a repository that I've
seen is to show the revision history and I don't really see a good
reason for change. Not that it's such a problem, it is only one more
click, but it is just not the expected behavior AFAICT from every other
implementation I've seen.
there is no freeform search text
entry box for the ticket system on the opening page
Use the general search box at the top. You can limit its search results
to just Tickets.
This is actually easier because it can be done from the very first page,
but it's not what people are used to...this change is very much welcome
for simplicity, but again, just not what is expected.
Also, there is no key for the color codes used in the lists. This seems
a very silly oversight and should definately be fixed.
Hmm. Interesting. I hadn't thought of that. I figured it would be clear
that the 'warmer' colors are higher priority than the 'cooler' colors.
It is to me...when looking at it in firefox. I've not checked with
links yet. :-)
Anyway, that's for upstream, I think.
Maybe for upstream, but how difficult is it to drop in a picture? And
what about those that have an inability to see colors? Priority and
severity text should definately be added to each line in addition to
color (this part _is_ probably an upstream issue unless the field
definitions can be easily changed).
The login button does not provide a link to create a new (unprivelaged)
account...may not be possible.
There's a plugin to allow this, but I'm not sure we want to. I think
it's a good thing to restrict access to known users only.
Ticket append is not turned on right now for anon users,
The above two problems go hand and hand. Ticket append should probably
_not_ be turned on for anonymous users. Just give athenticated users
the 'append' permission to existing issue tickets so that you have to
register. The registration can be automated with a conformation email
that should be answered before granting any account the login priveledge
(to keep from relying on the honesty system). I have no idea how
difficult the above suggestion is to implement.
>> but the defaults for ticket
>> entry
>> must be changed....see The 'TEST TICKET' in BLFS tickets to see the
>> curent defaults.
Actually, if users open tickets high and high, we might see the new
tickets more quickly, but I worry that behavior will be expected, and
users that take the time to properly rate issues will not get results as
quickly as those done incorrectly. Thats probably stretching it a bit
though as I usually don't see new bugs that way, but rather by the the
book mailing list.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
