[10] in Project_DB
Re: scope of work by 2/15 seems doable
daemon@ATHENA.MIT.EDU (Mike Barker)
Fri Jan 31 23:48:38 1997
To: "Bruce R. Lewis" <brlewis@MIT.EDU>
Cc: project-db@MIT.EDU
In-Reply-To: Your message of "Fri, 31 Jan 1997 22:28:28 GMT."
<199701312228.WAA04324@kindness.MIT.EDU>
Date: Fri, 31 Jan 1997 23:48:34 EST
From: Mike Barker <mbarker@MIT.EDU>
Thank you for the report--I'm glad to see it.
One comment from a "paper" test I've done was that the summary (with
all projects) should be ordered in some way. The person I was testing
it with suggested by process, then alphabetically within process.
They thought it wasn't too important what the ordering was, as long as
it was obvious or explicit. They would prefer to be able to click the
heads of columns and get it sorted on that column, but having some
known ordering was thought to be important.
Another comment was that if the docs or issues are separate buttons on
the project information display, when you go to "modify project" the
docs and issues should also become automatically "modify docs" and
"modify issues" -- i.e., in my paper version I just had docs and issues,
and it looked as if they would do two steps - select docs, then select
modify. should be one step if possible.
incidentally, I didn't see any mention of the issues fields?
I'd be interested in getting an updated "picture" of the pages so that
I can do some more "run throughs" with possible users.
thanks
mike
-> add button to show project documents
-Should show them on project display.
->Documents that exist for a project are currently not displayed on the
->project page. They should.
-I agree. User shouldn't have to press a button.
question? are these links to documents (which live elsewhere) or actual
documents? I'm concerned about a large project with many documents--it
may not make sense to display the entire list of documents in all cases?
->Submit status display adds:
-> button to create another project
-> button to go back to summary page. (DONE)?
-These are easy, and I will do them. However, I recommend people use the
-Back button on their browser if they want to keep their history list and
-back button usable. (This is a general WWW navigation tip.)
Good point--what we really want the user to do is hit back once, then
clear the form if they want to do multiple projects, or hit back again
if they want to get out of the create project "mode". too bad the buttons
in the web pages can't tell the browser what to do...
how about instead of breaking the www model, we provide a bit of
instruction on how to do another or quit?
->Separate pages for:
-> Ideas -- view ideas; view an idea; submit a new idea; delete an
->idea; submit comment. Note: Idea manager is postponed until project
->page up.
-I don't see what functionality is proposed here that doesn't exist with
-an archived mailing list. Unless there's a proposed way to
-systematically convert ideas into projects, I think it would be best to
-scrap the "idea" database and use a mailing list instead.
the only added thing I see is "threading" ideas and comments--and I agree,
that isn't that big a thing (some archived mailing list stuff provides it)
I agree with Bruce on this--let's keep the Projects Database as clean
as possible for now.
mike
