I've upgraded Kim's bug http://issues.collectionspace.org/browse/CSPACE-6075 to a blocker, as it rolls back previously available functionality (in a way). Question - with contributed code, who fixes the bug? -- Megan Forbes Director of the Collection Museum of the Moving Image 36-01 35 Avenue Astoria, NY 11106 movingimage.us 718 777 6800 Direct 718 777 6834

Megan, et al., Well, it's not really my place as a deployer to have an opinion, but .. I do! If the contributor cannot fix the bug (and it is possible that they might not have the resources or skill, or may no longer be available, or not available in a timely way), then the "core team" would have to either fix it or reject (back out) the contribution, right? In fact, the fix itself would have to be vetted and accepted the same way the original contribution was vetted and accepted, wouldn't it? Indeed, the "fixer of last resort" will always have be the "core team", I think, no way around it! John On Fri, Jul 5, 2013 at 11:53 AM, Megan Forbes <mforbes@movingimage.us> wrote: > I've upgraded Kim's bug http://issues.collectionspace.org/browse/CSPACE-6075 > to a blocker, as it rolls back previously available functionality (in a > way). > > Question - with contributed code, who fixes the bug? > > -- > Megan Forbes > Director of the Collection > > Museum of the Moving Image > 36-01 35 Avenue Astoria, NY 11106 > movingimage.us 718 777 6800 > Direct 718 777 6834 > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

Agreed generally with John. In this particular case, SMK's contribution of the Citation Authority was also vetted and integrated by the core team, so at this point, I'd argue that the core team (in this case, me) is entirely responsible for fixing the bug. I've assigned CSPACE-6075 to myself and am looking into it now. At a quick first glance, I'm expecting/hoping this is simply a matter of Services layer configuration, or at most a code fix in that layer; non-preferred terms don't seem to currently be emitted in Services list results. Unless my memory is worse even than even my worse fears, this *was* working at some point during the integration; I distinctly recall having tested that non-preferred terms appeared but were grayed out and couldn't be selected in the Lifesci tenant. *Sigh* Aron On Fri, Jul 5, 2013 at 2:08 PM, John B. LOWE <jblowe@berkeley.edu> wrote: > Megan, et al., > > Well, it's not really my place as a deployer to have an opinion, but .. I do! > > If the contributor cannot fix the bug (and it is possible that they > might not have the resources or skill, or may no longer be available, > or not available in a timely way), then the "core team" would have to > either fix it or reject (back out) the contribution, right? > > In fact, the fix itself would have to be vetted and accepted the same > way the original contribution was vetted and accepted, wouldn't it? > > Indeed, the "fixer of last resort" will always have be the "core > team", I think, no way around it! > > John > > On Fri, Jul 5, 2013 at 11:53 AM, Megan Forbes <mforbes@movingimage.us> wrote: >> I've upgraded Kim's bug http://issues.collectionspace.org/browse/CSPACE-6075 >> to a blocker, as it rolls back previously available functionality (in a >> way). >> >> Question - with contributed code, who fixes the bug? >> >> -- >> Megan Forbes >> Director of the Collection >> >> Museum of the Moving Image >> 36-01 35 Avenue Astoria, NY 11106 >> movingimage.us 718 777 6800 >> Direct 718 777 6834 >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org