As you know, I *love* communication. More than coding, obviously. :) But the difficulty with splitting a single conceptual function across multiple teams, multiple repositories, and multiple JIRA tasks is that there may be no way to know who to communicate with or even necessarily what question to ask (and also, of course, no guarantee that the person you need to communicate with is attending at that moment).
Going back to my list of recent representative examples, how was a client-side developer to know that there was a better way to get "related content" tucked away in the Nakamura source tree? By sending an email to oae-dev? Moving every such work item to the mailing list will get really old really fast. By having every Nakamura developer carefully monitor the 3akai-ux JIRAs and vice-versa? Had we but team enough and time (and extremely clear and detailed JIRA descriptions), maybe. The "no redundant wildcards" message pounded like deep dub throughout team meetings and emails in late 2010. But it still got lost between then and now without anyone noticing because we were all assigned work that didn't include noticing such things. (And also because the solution implemented at the time encouraged risky behavior from client-side code, but still....) Best, Ray On 4/27/12 7:13 AM, Daniel Parry wrote: > On Thu, Apr 26, 2012 at 10:33:19AM -0700, Ray Davis wrote: >> Our experience to date shows that structured queries (whether they're >> Solr or plain Lucene or SQL) need to receive focused attention from >> knowledgeable human beings. I don't see how that can happen when a query >> combines bits and pieces of code created by separate development teams >> at separate times. > > Communication? > > Best wishes, > > Daniel > _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
