[Board] Stolen computer

Thu Aug 3 09:10:23 PDT 2017

This motion did not pass - sadly it did not pass because the board members
disagreed; it did not pass because not enough board members responded to
the motion.

https://www.loomio.org/p/TA0rPawq/offer-financial-assistence-to-nick-and-niroshan-to-cover-insurance-costs-of-stolen-laptops-

This is a non-result that does not set a precedent for future boards.

--
Jody Garnett

On 27 July 2017 at 06:05, Jody Garnett <jody.garnett at gmail.com> wrote:

> Cameron and Michael your words of caution are very much taken to heart.
>
> Maria has started a motion here
> <https://www.loomio.org/d/csZ2X8ap/stolen-computers-at-foss4g> and I am
> copying my words to email for wider discussion:
>
> *I am in favour of us helping assist in this case, but I understand their
> is a series of groups, including the local organizing committee who would
> like to help out. I would be the most comfortable with the local organizing
> committee (or even the rented venue assisting.)*
>
> *We have been cautioned about "setting a precedent" last time the board
> acted in a generous fashion outside of our mission statement (since we are
> responsible for our actions to our membership which elected us). In this
> case the people effected individuals are both productive members of our
> volunteering in an official capacity with our organization: one as a summer
> of code student, and the second as a member of the marketing committee. I
> believe our membership will understand why we are making this choice.*
>
> *While it may be sad in the future if trouble befalls an attendees at one
> of our events we do not wish to set a precedent or expectation for future
> events to follow. We are taking action both out of compassion (this sucks)
> and these individuals our volunteers in our organization we do not want our
> membership to loose the benefits of their productivity (this sucks for
> osgeo). This is in a similar spirit to the liability insurance we hold for
> our board members and officers.*
>
> And on the specifics:
>
> *From the email thread it sounds like both computers are covered by
> insurance, but not the full costs. There are two ways to understand this
> email:*
>
>
>    - *For a $2500 computer, perhaps it was only insured for $2000 (often
>    this is fine as computers get older).*
>    - *Or perhaps it is a "deductible" - for example for a $2000 computer
>    there may be a $500 deductible needing to be paid. So while the insurance
>    covers everything, you are required to pay $500 to access the insurance.*
>
> *I would be comfortable making a proposal making up to $2000 available to
> the treasurer to assist with paying any insurance costs incurred while
> replacing the stolen laptops. Subject to "prompt reimbursement" on receipt
> (if paid for already) or invoice (if there is an email/bill that can be
> sent to the treasurer to show the amount needed).*
>
> This is the kind of discussion is difficult because we all have the "it
> could of been me" response, and general annoyance this incident would
> reflect poorly on our community (even though it is not our fault). It also
> paints board members into a bit of a corner; because we do not wish to
> appear mean / heartless / insensitive (cameron's all things to all people).
>
> --
> Jody Garnett
>
> On 27 July 2017 at 04:16, Michael Terner <mgt at appgeo.com> wrote:
>
>> + Conference Dev
>>
>> Two very small points from the Boston perspective as these kinds of
>> things are on our mind, and we are seeking lessons learned to improve our
>> event:
>>
>>    1. Insurance can be expensive. We have an insurance policy that does
>>    not cover things like lost/stolen items for attendees, but does cover
>>    eventualities like needing to cancel the event due to catastrophe. The cost
>>    of a policy covering lost/stolen events - at least for an event the size of
>>    Boston - would have been significantly higher than the cost of replacing 2
>>    laptops (and there is additional administrative time in setting it up).
>>    2. This incident also illustrates the need to have appropriate
>>    physical security. We will be mindful to not leave our registration desk
>>    without someone there; and to discourage people from leaving items in
>>    places where there are not people actively watching. We also have access to
>>    a couple of locked rooms where things can be stored and will encourage
>>    their use to the extent possible.
>>
>> We too regret the hassle, inconvenience and loss that Nick and Niroshan
>> experienced. As with all negative things, hopefully there is a silver
>> lining and this community can improve processes to reduce the risks of loss
>> at conferences...
>>
>> MT
>>
>> On Thu, Jul 27, 2017 at 4:46 AM, Cameron Shorter <
>> cameron.shorter at gmail.com> wrote:
>>
>>> I'll let others comment on this particular thread. It is very sad to
>>> hear of people having a computer stolen and noble to hear of people helping
>>> those in need.
>>>
>>> But on a general level, I suggest that OSGeo should be careful not to
>>> become all things to all people. We should focus on what we are best at.
>>> There are insurance companies designed to manage loss of items. For future
>>> incidents of this type, lets make use of them rather than designing our own.
>>>
>>> Cheers, Cameron (not a current board member, so my vote doesn't count)
>>>
>>>
>>> On 27/7/17 12:21 am, Jeff McKenna wrote:
>>>
>>>> Thank you Luca for bringing this to everyone's attention.  Indeed this
>>>> was a very unfortunate incident.  I am a strong +1 to help Niroshan and
>>>> Nick in any costs not covered by insurance.
>>>>
>>>> The day before this happened I also left my bag for a few hours behind
>>>> the registration desk; this could have happened to anyone.
>>>>
>>>> This kind of thing has been at the back of my mind for a while now; how
>>>> lucky we have been for accidents at FOSS4G events.  We travel to areas all
>>>> around the world, and anything can happen. Luckily Niroshan or Nick were
>>>> not hurt or injured.
>>>>
>>>> It might be a good time to review the event insurance for our FOSS4G
>>>> events, and how it relates to unfortunate accidents like this.  (and how we
>>>> would handle the cases if the attendee had no personal insurance, which
>>>> would have been my case - for example, maybe the OSGeo Board should set
>>>> aside a small block of funding in each yearly budget for this)
>>>>
>>>> But my gut feeling is that was a small warning, as our FOSS4G event
>>>> grows in popularity, we must take care, to take care of our attendees.
>>>>
>>>> I am very sorry for such a hassle to Niroshan and Nick, to their
>>>> studies and their work.  I hope we can agree to make sure that they have to
>>>> pay nothing out of their own pockets to replace lost equipment; and also
>>>> agree to take this as a small lesson and review our own event policies.
>>>>
>>>> -jeff
>>>>
>>>>
>>>>
>>> --
>>> Cameron Shorter
>>> M +61 419 142 254
>>>
>>>
>>> _______________________________________________
>>> Board mailing list
>>> Board at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/board
>>>
>>
>>
>>
>> --
>> *Michael Terner*
>> *Executive Vice President*
>> 617-447-2468 <(617)%20447-2468> Direct | 617-447-2400 <(617)%20447-2400>
>> Main
>> Applied Geographics, Inc.
>> 24 School Street, Suite 500
>> Boston, MA 02108
>> www.AppGeo.com
>>
>> This e-mail message and any attachments may contain confidential or
>> legally privileged information. If you are not an intended recipient or
>> otherwise authorized to receive this message, you should not use, copy,
>> distribute, disclose or take any action based on the information contained
>> in this e-mail or any attachments. If you have received this message and
>> material in error, please advise the sender immediately by reply e-mail and
>> delete this message. Thank you on behalf of Applied Geographics, Inc.
>> (AppGeo).
>> _______________________________________________
>> Board mailing list
>> Board at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/board
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20170803/79780971/attachment.htm>