Re: Prelminary bug web interface now up - for testing only.

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:On Thu, September 22, 2005 4:49 am, Matthew Dillon said:
:
:> 	* Attachments: uploads and hotlink downloads.  Currently handles
:> 	  100% binary attachments and can retain the mime type, but probably
:> 	  needs tuning to prevent it from being used by spammers/pornsters.
:
:Since this is not unlike a wiki, it would be worthwhile to create a "view"
:of edits by a given user, or within a given timeframe.  This way if a
:registered or unregistered user decides to vandalize/spam across a large
:number of items,  it is easier to seek out and remove those events.
:
:What's the difference in purpose between Edit and Append?  (Other than
:seeing other appends when editing?)

    'Append' is just if you want to append an addendum.   'Edit' will
    bring up every entry for the bug and the pieces you have access to
    will be editable... the screen can get quite busy.

:Release version and processor count ought to be separated - they are
:related data, but it's syntactically confusing to have two separate
:descriptive items in one toggle.

    I think you're right.  The operating system 'uname' info should
    be independant of the rest of the machine configuration info
    (there's no UI to add your own machine configs yet so all you are
    seeing are the defaults I threw into the database).

:Can something be created in the database to associate "help topics" with
:given parts of the database - specific fields, or actions?  As it stands,
:explanation of the intention behind each action or piece of data is going
:to have to be a separate document; having it integrated into the
:application will reduce the amount of labor and time a user (especially a
:casual user) will have to do for clarification.

    Help topics would be at index 99 on my 1-100 list.

    Once I clean up the formatting of the tables (they can look pretty ugly)
    the bugs will be less confusing.  I am going to add some fixed-width
    fields and move the comment into its own table space.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>