|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
Pre-meeting reading and questions for Fluid Engage all-handsHi All,
In preparation for next week's Fluid Engage all-hands meeting in Toronto you may want to familiarize yourself with some of the following information: Project Background: These links will give you a general background in Fluid Engage, Fluid, and the current work of the Project Team. A PDF of the full Fluid Engage grant document http://wiki.fluidproject.org/download/attachments/6816660/Fluid+Engage.pdf?version=1&modificationDate=1239224595000 The Fluid website http://fluidproject.org/ For those interested in all the projects the Fluid community is working on (including CollectionSpace) http://fluidproject.org/projects/ The current work the Project Team is doing http://wiki.fluidproject.org/display/fluid/Fluid+Engage+Roadmap+Q2 Design links: We are hoping for a lot of feedback on our early scenarios. Scenarios are a tool used by our design team to structure the work around a particular problem as expressed in a hypothetical situation. http://wiki.fluidproject.org/display/fluid/Mapping+scenarios http://wiki.fluidproject.org/display/fluid/Mobile+scenarios Technical links: If you want to see code, have a look at the Fluid Infusion package. The information page for our product: Fluid Infusion http://fluidproject.org/products/infusion/ Some of the questions we hope to cover are: From the Fluid Project Team: How does Fluid support Fluid Engage? what do all the groups/ committees mean? What will Fluid Engage build? what problem are we solving? and how might it help or be used? How will the Project Team do the work? From the Advisory Panel and museum partners: How can the Advisory Panel contribute and help? How best can we all share information and communicate? about our goals and progress? Help the team understand some of the most critical things that need to be done in museums at the moment (within the context of the web, mobile, and physical spaces the project proposes to work within) What are the essential things that Fluid Engage needs to cover? What hasn't worked, but also what *has* and how might we learn from your experiences in our work on Fluid Engage We are excited to have everyone in Toronto next week to begin some of these discussions. This meeting is our opportunity to begin conversations with you, to clarify what we are doing while getting early feedback from you, and to work out how we will continue discussion, participation, and information sharing. If you have any questions, please feel free to let me know. Jess ~~~~~~~~~~~~~~~~~~~~~~ Jess Mitchell Boston, MA, USA Project Manager / Fluid Project jess@... / w / 617.326.7753 / c / 919.599.5378 jabber: jessmitchell@... http://www.fluidproject.org ~~~~~~~~~~~~~~~~~~~~~~ _______________________________________________________ fluid-talk mailing list - fluid-talk@... To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-talk |
|
|
foward into thte past -- eDocent planning documentsGreetings Fluid Engagers,
In what may be a continuing dialogue with myself, I want to call your attention to a storehouse of process documents that were generated as part of the eDocent prototype project from 2000. These documents, especially the Discovery and Engineering Deliverables, will be of most interest to the FE engineering and design teams. IMHO they are surprisingly resilient to the ravages of Internet Time. For the project, the team from Organic (led at the time by the tremendously talented Robert Fabricant and Ben Cerveny) applied a user-centered design methodology that parallels the process in which we'll all be, ahem, engaged. We focused not on developing a device, but on leveraging the personal, network-aware mobile media devices that the public would surely bring with them to museums one day, and which can serve as connective tissue between onsite and online museum visits. We missed a lot of things. The Museum team firmly rejected, for instance, the Organic team's plea to build a social networking component and elements of play into the prototype experience. Against all reason, this project almost turned into a business (this *was* the dusk of internet bubbletime after all) and then 9/11 intervened. Here's the link: http://wiki.fluidproject.org/display/fluid/eDocent+%28Museum+of+the+Movi ng+Image%29 Take a look before whomever runs Organic tells us to take it down. See y'all Monday. cheers, Carl Carl Goodman Senior Deputy Director Museum of the Moving Image _______________________________________________________ fluid-talk mailing list - fluid-talk@... To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-talk |
|
|
Re: foward into thte past -- eDocent planning documentsJust a note, you do need to be logged into the wiki to access this page. If you do not already have a wiki account you'll need to create one. Best, Jess ~~~~~~~~~~~~~~~~~~~~~~ Jess Mitchell Boston, MA, USA Project Manager / Fluid Project / w / 617.326.7753 / c / 919.599.5378 jabber: jessmitchell@... ~~~~~~~~~~~~~~~~~~~~~~ On Jun 19, 2009, at 10:02 AM, Goodman, Carl wrote:
_______________________________________________________ fluid-talk mailing list - fluid-talk@... To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-talk |
| Free embeddable forum powered by Nabble | Forum Help |