> On Apr 2, 2019, at 12:11 PM, Daniel Gruno <humbed...@apache.org> wrote: > > > The specific organizational structure does indeed seem like a moot topic. > What matters is that wherever this take place, the group is given *space and > freedom* to get some work done. I'd be fine with it being within ComDev, I'd > also be fine (but perhaps a bit confused) with it being a thing of its > own...but what it really just needs is a space to work within, and a > sufficient amount of isolation from bike-shedding. > > I'd recommend a separate mailing list (to provide focus) and a JIRA, perhaps > some place to put documents (either within the comdev svn area, or somewhere > else if spun off), and then...just get to work :) >
My last post on this today: Agreed on the above. The rationale for keeping in ComDev is to avoid friction and possible "hey, shouldn't D&I be doing that?" and "Hey, this is part of ComDev", etc... keeping all under one roof prevents that whereas sep mailing list and Jira allow for the potential for focus to keep the effort going. As the lines become more clear on what are the diffs between ComDev's charter and what D&I is doing (if it comes to that), then that friction/overlap/confusion becomes moot.
