On Wed, Jul 10, 2013 at 4:07 PM, Kathy Lussier <kluss...@masslnc.org> wrote: > Hi all, >
[snip] > > Defining Evergreen services: I'm open to not defining what an Evergreen > service is and to see how it goes. My personal preference is that Evergreen > support providers not be confused with third-party services that integrate > with Evergreen, even if that third-party vendor needed to learn a lot of the > code to get their service to work with Evergreen. Using Rogan's example, I > don't think people come to this page looking for blue tooth scanners, so > those vendors shouldn't be listed on this page. > Just to clarify, Iwas specifically /not/ talking about the bluetooth scanner-type example, about which I agree 100%. If the consensus is that actively involved 3rd party vendors should be separated from direct Evergreen service providers, that's fine, but I just want to be clear about the sort of provider I was referring to. Were I looking at Random OSS Project X's web site, I'd prefer to have one "folks I can pay (after vetting) to get stuff done" page, which seems to be how ours is used. I'd include 3rd party products from vendors with "skin in the game" in that set. -- Mike Rylander | Director of Research and Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@esilibrary.com | web: http://www.esilibrary.com
