JIRA project division: Fluid Infusion vs Floe
obara.justin at gmail.com
Mon Mar 12 17:22:52 UTC 2012
I think it makes sense to keep things separate. I'm not fully versed in what will be going into FLOE at this point, but I understand there some areas that are a bit ambiguous. I guess we just have to keep in mind if it will be shipping with Infusion or not. In the worst case, we can always move jiras between projects.
On 2012-03-12, at 11:10 AM, Colin Clark wrote:
> Hi James,
> I don't know if anyone else had thoughts on this; I always defer to Justin on these sorts of issues. But I don't see any reason not to create a new space in JIRA for Floe. The Video Player needn't cause us too much trouble--we imagine it will be part of Infusion some day, so it's already in the right place in JIRA.
> My two cents,
> On 2012-03-08, at 4:23 PM, James W. Yoon wrote:
>> In preparation for updating the design svn with a backlog of work the design team's been doing, I've come across an issue of what JIRA project to associate the commits with. Until now, we've been associating it with Fluid Infusion, but much of the work we've been doing (e.g., UI for ISKME's OER Commons authoring tool, Universal Subtitles UX review work, etc.) is only indirectly related to Infusion.
>> As I see it, our options are to either:
>> 1) Continue to use Fluid Infusion as the space for Floe design work (which may be diluting Fluid Infusion with less related JIRAs), or
>> 2) Carve out a Floe space in JIRA (which would bring up questions of where to put cross-relevant JIRAs; e.g., the video player work)
> Colin Clark
> Technical Lead, Fluid Project
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
More information about the fluid-work