Bugzilla – Full Text Bug Listing
| Summary: | Revisit project, workspace, and file system terminology | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Client | Assignee: | Susan McCourt <susan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.5 | ||
| Target Milestone: | 0.5 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Susan McCourt
Aaaaaaaaaaaarrrrrrggggggggghhhhhhhhhhhhhhhhhhhhh!!!!!!!! (In reply to comment #1) > Aaaaaaaaaaaarrrrrrggggggggghhhhhhhhhhhhhhhhhhhhh!!!!!!!! "Create New Aaaaarrrrrgggggghhhhhhh" ??? seriously, though, are you saying we should just call it a "Folder"? There is something that just keeps bugging me about this. > "Create New Aaaaarrrrrgggggghhhhhhh" ???
I've been involved in discussions over the meaning of "project" and "workspace" for over ten years now... that was the sound of me jumping out of the window after reading the bug title. Luckily I only work on the 4th floor so I am feeling better today and can maybe say something more constructive.
It is true that "file systems" will be exposed more and more, so we do need a good story to describe that level of container. I am completely open to ideas there. My first impression is "file system" is a bit too low level. Typically "adding a file system" is something done by Unix administrators rather than web developers. I wonder if we could use a more general term like "Places", "Sources", or "Collections"... something that expresses they are not co-located with each other. I think each file system should be exposing a good name and distinctive icon for itself, ideally including the host name where applicable. In theory I could add file systems from orion.eclipse.org and orionhub.org in a single Orion instance, so they would need to be differentiated. I imagine a section on the LHS like this:
Sources:
+ mamacdon on Amazon S3
+ orion.eclipse.org
+ Local Storage
... etc ...
I would be curious to hear from others who might be less encumbered by semantic baggage over these terms... maybe a topic for the next UX call?
Just to clear up a minor misconception, you said "Under the covers, we have eclipse workspace projects". To be clear, we have no vestige of Eclipse desktop workspaces and projects on the server. There is only a single workspace ("instance location") on the server shared by all users. There is a very simple Orion project model that is unrelated to the old one in Eclipse. A project on the Orion server is really a small bit of metadata linking a file system location to a name and a set of user permissions (saying which users can read/write that file system location). This doesn't affect the naming discussion from the Orion client end user perspective but just wanted to avoid confusion.
(In reply to comment #3) Thanks, John. (my second reaction to Aaaaaaaaaaaarrrrrrggggggggghhhhhhhhhhhhhhhhhhhhh!!!!!!!! was...."perhaps he was dictating!") You bring up a good point, we are talking about three terms here. 1) what is a "file system"? We show this word in the "File Servers" list in the nav when more than one is installed. Agree we need a better, more user oriented word. The trick is that generic words like "Collection" sound as if the user should be able to control the grouping. So "Places" might be a better word for now, perhaps some folks have better ideas. (I was just talking to Mark about the fact that in an ideal world, this term is NEVER exposed in the UI when only one file system is present. The user shouldn't have to know "oh, I have one Place" if they don't have the ability to use another kind of Place") 2) what is the "top level folder of a file system" called? The key here is that you can only create a top level folder when you are in the root of a "Place", and it may have special capabilities (like the ability to link one, or creating one by cloning a repository.). In Eclipse we called this a "Project." Early on in Orion we just called it a "Folder" since it wasn't very special. But exposing the automatic content creation (create from clone, etc.) seems to warrant a more specific noun. The word "Content" was the closest thing I could think of, but maybe "Project" is fine. 3) We need a name for the "root" of a "Place." Since this root segement shows up in the breadcrumb, etc. all the time (even when there is only one file system installed,) I like the idea of using the term in #2 rather than #1. So the name of the Orion file system would be: "Orion Projects" or "Orion Content" rather than "Orion Place" In the interest of consistency, I'll take this bug for M2 and do the following: - file system names will use "Content" instead of "Projects" - file system list will say "Places" instead of "File Servers" - this aligns with "Create new content" - I'll change some of the implementation folders like "projectTemplates" to "contentTemplates" so that we are consistent in our code (In reply to comment #5) > In the interest of consistency, I'll take this bug for M2 and do the following: > > - file system names will use "Content" instead of "Projects" > - file system list will say "Places" instead of "File Servers" > - this aligns with "Create new content" > - I'll change some of the implementation folders like "projectTemplates" to > "contentTemplates" so that we are consistent in our code all done. I changed the Orion file client and the webdav client to use the name "WebDAV Content" and "Orion Content" cc'ing Mark. You may want to rename the S3 plugin to something that looks good in a breadcrumb root (if it's not already.) |