On Tue, Dec 30, 2008 at 6:10 PM, eric.bachard <[email protected]> wrote:
> Art is important too, your right, but I more think this is a multi-projects > affair. Don't know who should coordinate though (probably marketing after > some reflexion) [I don't claim to know how the Art team functions now, so if I am repeating an existing workflow, please do excuse the ignorance] If the Art team has a workflow in place (via an issue-tracker for example) to accept 'assignments' from other sub-projects, it would indeed work out to be a nice system. Sub-projects need content as does Marketing and the MarCons who would be happy to be part of this process by requesting some locally relevant tweaks. The co-ordination is more a function of collaboration rather than a top-down directive. At least, that is how I look at it. >> So, if sub-projects talk with the Artwork teams > > This is the right way, indeed. But it does suppose Art asked or started > something with Education Project in this case ? Not really. As a conjecture, if we say that the Art team defines look-n-feel, Marketing tweaks messaging and the sub-project collaborates with both, it would be a function of constant communication rather than ad-hoc, event driven content generation. > I agree with that. What I disagree is how Education Project was "simply" > ignored. I would like to take a longer term workflow based approach :) and not limit the discussion to the specific case. The lack of existing handouts (for reasons that are not relevant now) may have forced creating a content. Let's just make a quick move towards within_project collaboration :) ~s -- You see things; and you say 'Why?'; But I dream things that never were; and I say 'Why not?' - George Bernard Shaw --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
