Proposed design svn structure
James William Yoon
james.yoon at utoronto.ca
Tue Oct 20 14:51:02 UTC 2009
Thanks for the comments, Leah!
Jess is right about keeping Design out of the Engage space. To provide
additional reasoning: I think it's best we isolate the design files
from the code. The expectation right now when one checks out /fluid in
svn is that they're getting all the code-related things for Fluid
(scripts, markup, style sheets, etc.). There are fairly strict
conventions governing the file/folder names, structure, and what
belongs and doesn't belong in there. Mixing in our design files would
probably add confusion.
In terms of papers and presentations, there certainly is a space in
the wiki for that, but I think, despite the redundancy, that there's
value in putting them into the repository as well (having a
consolidated area where all our design-related files live is part of
the what the repository was all about!). Let's talk more about that
this afternoon at the design meeting.
(side note: Vicki and I discussed whether we could put design and
museum papers generally related to our project in the repository--I
was all for the idea of having a convenient library of papers in the
repository, until I realized we'd probably be breaking copyright laws)
On Mon, Oct 19, 2009 at 12:53 PM, Jess Mitchell <jess at jessmitchell.com> wrote:
> Design should live outside of Engage since we have plenty of design work for
> other projects. If we keep it Design > Engage, that allows us to have
> Design > Other Project in the future. We can easily grow with that.
> Powerpoints and papers should go into the wiki on the Presentation page. It
> might be useful for us to talk about what kinds of materials we expect to
> put in SVN versus the wiki in our conversation this afternoon.
> Jess Mitchell
> Boston, MA, USA
> Project Manager / Fluid Project
> jess at jessmitchell.com
> / w / 617.326.7753 / c / 919.599.5378
> jabber: jessmitchell at gmail.com
> On Oct 16, 2009, at 5:55 PM, Leah Maestri wrote:
> Hi James,
> This looks really good. The only question I have is for the first 4
> directories. It goes svn/, then design/, then engage/... etc. Is the reason
> for why design/ lives outside of engage/ because it's more related to the
> entire fluid project and not specific to engage/? I guess in my mind all the
> design work that we're doing is within engage/. Correct me if I'm wrong.
> What about materials from conferences (i.e: powerpoints, papers, etc.) would
> that go under one of the following?
> Great stuff!
> On Fri, Oct 16, 2009 at 1:49 PM, James William Yoon <james.yoon at utoronto.ca>
>> Hello all (but especially designers, since this affects you most!),
>> Vicki and I spent the afternoon thinking about the sorts of files we
>> have as FE designers (wireframes, stencils, pixel-perfect mockups,
>> fonts, academic literature on UX/IxD and museum stuff, museum maps,
>> testing protocols, ethics and consent forms, the journey frameworks
>> and ontology, etc.), and then hacked away at the structure of our
>> design svn.
>> Here's what we're proposing:
>> /svn (the root)
>> /design (where the designers live)
>> /engage (where Fluid Engage lives)
>> /admin (general administrative files--project
>> description, contact info, etc.)
>> /mobile (mobile micro-project)
>> /stencils (mobile wireframes toolkit)
>> /kiosk (kiosk micro-project)
>> /stencils (kiosk wireframes toolkit)
>> /resources (general designer toolkit and other
>> Engage-specific resources)
>> /process (design process stuff, like the Journey
>> Frameworks and Ontology)
>> /etc (everything else)
>> /decapod (where Fluid Decapod lives, if they so desired)
>> /collection-space (where CSpace lives, if they so desired)
>> Your thoughts, questions, and suggestions would be very helpful. In
>> particular, ask yourselves whether you have (or will have) files that
>> don't fit under this structure, and, more importantly, whether this
>> structure makes sense to you.
>> Developers, you all have much more experience than us in svn--does the
>> structure make sense? Any potential svn snafus we should be aware of?
More information about the fluid-work