<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2016/03/16 19:19, Massimiliano
Cannata wrote:<br>
</div>
<blockquote
cite="mid:CAMKYQEv68QPuR-N0Afs2O-1srYXOpjjhWC4KbQ6ysXeLsX9JfA@mail.gmail.com"
type="cite">
<pre wrap="">Dear all,
my vote is +0
You may know, since last year, i'm not inclined to take any risk and sign
anything before the current FOSS4G is closed.
I don't like to be exposed two time.
Anyway, said that my vote is expressed, I have a request related to risk:
- What about US FOSS4G conference in 2017?
- Do you have any information on this?</pre>
</blockquote>
<br>
FOSS4G-NA will not be held in 2017 [1].<br>
<br>
best<br>
<br>
Venka<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/pipermail/conference_dev/2016-March/003650.html">https://lists.osgeo.org/pipermail/conference_dev/2016-March/003650.html</a><br>
<br>
<blockquote
cite="mid:CAMKYQEv68QPuR-N0Afs2O-1srYXOpjjhWC4KbQ6ysXeLsX9JfA@mail.gmail.com"
type="cite">
<pre wrap="">
Maxi
</pre>
<blockquote type="cite">
<pre wrap="">
2016-03-16 9:35 GMT+01:00 Dirk Frigne <a class="moz-txt-link-rfc2396E" href="mailto:dirk.frigne@geosparc.com"><dirk.frigne@geosparc.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">I already responded to the answers we've received. So:
+1 to approve request for FOSS4G 2017
I also want to investigate how we can get an insurance for such an
additional guarantee for future events. Who is in a good position to
take here some action and get some information. Do we have a volunteer
who can take action here?
Dirk
On 16-03-16 03:08, Michael Smith wrote:
</pre>
<blockquote type="cite">
<pre wrap="">----
Michael Smith
OSGeo Foundation Treasurer
<a class="moz-txt-link-abbreviated" href="mailto:treasurer@osgeo.org">treasurer@osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:treasurer@osgeo.org"><mailto:treasurer@osgeo.org></a>
From: Board <<a class="moz-txt-link-abbreviated" href="mailto:board-bounces@lists.osgeo.org">board-bounces@lists.osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:board-bounces@lists.osgeo.org"><mailto:board-bounces@lists.osgeo.org></a>> on behalf of Venkatesh Raghavan
<<a class="moz-txt-link-abbreviated" href="mailto:raghavan@media.osaka-cu.ac.jp">raghavan@media.osaka-cu.ac.jp</a> <a class="moz-txt-link-rfc2396E" href="mailto:raghavan@media.osaka-cu.ac.jp"><mailto:raghavan@media.osaka-cu.ac.jp></a>>
Date: Tuesday, March 15, 2016 at 7:47 PM
To: OSGeo Board <<a class="moz-txt-link-abbreviated" href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><mailto:board@lists.osgeo.org></a>>
Subject: Re: [Board] [OSGeo-Conf] 2017 Boston agreement & seed funding -
IMPORTANT
Dear Board,
</pre>
<blockquote type="cite">
<pre wrap=""> MOT7: Seek additional clarifications and attend to this agenda
item by e-mail within 7 working days
</pre>
</blockquote>
<pre wrap="">
Pending the approval of the above motion moved at
the Board meeting held on 10 March, I would like to
remind that we have two working days remaining
to seek further clarification concerning the
2017 Boston agreement & seed funding request and
vote for board approval.
Considering the time available and also the fact that I
do not intend to seek further clarification from my side,
I would like to move the motion to approve the request
from BLOC.
+1 to approve request for FOSS4G 2017
Best
Venka
On 2016/03/15 21:17, Michael Terner wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Venka:
Thanks for the fair questions and thanks to the board for the
</pre>
</blockquote>
</blockquote>
<pre wrap="">serious
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> consideration of our request.
Steven, thanks for the general outline of a response and an
</pre>
</blockquote>
</blockquote>
<pre wrap="">enumeration of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> our request. Your four points are entirely accurate and indeed
</pre>
</blockquote>
</blockquote>
<pre wrap="">several
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> people guided us to examine the Bonn agreement as a template for an
OSGeo/LOC agreement. This is precisely what we did, although in
</pre>
</blockquote>
</blockquote>
<pre wrap="">our case,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and unlike Bonn, the BLOC is not a legal entity and thus as with
</pre>
</blockquote>
</blockquote>
<pre wrap="">some past
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> conferences our PCO is part of the agreement as our "financial
</pre>
</blockquote>
</blockquote>
<pre wrap="">agent". So
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> here are a few additional details on the four main points:
1. *Names*: Our agreement has three parties: OSGeo, the Boston
</pre>
</blockquote>
</blockquote>
<pre wrap="">Location
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Organizing Committee (BLOC) and Delaney Meeting & Event
</pre>
</blockquote>
</blockquote>
<pre wrap="">Management, our
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> PCO, who is acting as our financial agent.
2. *Seed funding*: We are asking for approval of up to maximum
</pre>
</blockquote>
</blockquote>
<pre wrap="">of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> $70,000 of advances. As per the email threads, we anticipate
</pre>
</blockquote>
</blockquote>
<pre wrap="">doing this
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> through two separate requests. The first would be for $20,000
</pre>
</blockquote>
</blockquote>
<pre wrap="">+/-
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> immediately following our hoped for approval of the agreement.
</pre>
</blockquote>
</blockquote>
<pre wrap="">The second
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> would be for the remaining $50,000 after the Bonn Conference
</pre>
</blockquote>
</blockquote>
<pre wrap="">concludes and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> as we begin to ramp up at a faster pace (and as deposits come
</pre>
</blockquote>
</blockquote>
<pre wrap="">due).
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> 3. *Additional guarantee*: Again, we followed the Bonn
</pre>
</blockquote>
</blockquote>
<pre wrap="">agreement model,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and as Steven points out the "total exposure" for OSGeo between
</pre>
</blockquote>
</blockquote>
<pre wrap="">the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> advances and additional guarantee are the same for both Boston
</pre>
</blockquote>
</blockquote>
<pre wrap="">and Bonn. I
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> would also observe that the known precedent of OSGeo providing
</pre>
</blockquote>
</blockquote>
<pre wrap="">these
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> guarantees was something we considered strongly in forming our
</pre>
</blockquote>
</blockquote>
<pre wrap="">bid. Indeed,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> both the BLOC and OSGeo are "in this together" with substantial
</pre>
</blockquote>
</blockquote>
<pre wrap="">"skin in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the game" and we are both strongly motivated for a superior and
</pre>
</blockquote>
</blockquote>
<pre wrap="">financially
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> successful event. We will work tirelessly to ensure Boston
</pre>
</blockquote>
</blockquote>
<pre wrap="">continues the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> FOSS4G streak of being financially successful.
4. *Contractual clauses*: As has happened over the years, we
</pre>
</blockquote>
</blockquote>
<pre wrap="">would
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> certainly urge OSGeo to continue building on the template
</pre>
</blockquote>
</blockquote>
<pre wrap="">agreement and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> these clauses provide important *mutual *protections as well as
providing a framework for cost-effective dispute resolution in
</pre>
</blockquote>
</blockquote>
<pre wrap="">the unlikely
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> event it is needed. They are standard clauses, but they also
</pre>
</blockquote>
</blockquote>
<pre wrap="">articulate
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> important principles.
Last, please consider the BLOC to have a strong +1 to Dirk's
</pre>
</blockquote>
</blockquote>
<pre wrap="">suggestion
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> that OSGeo look at an insurance approach for FOSS4G that could be
</pre>
</blockquote>
</blockquote>
<pre wrap="">designed
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> to cover future events and could leverage the good financial
</pre>
</blockquote>
</blockquote>
<pre wrap="">record of past
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> FOSS4G's. This would be one more thing that the "next conference"
</pre>
</blockquote>
</blockquote>
<pre wrap="">(e.g.,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> 2018) would not have to start from scratch with. Along those
</pre>
</blockquote>
</blockquote>
<pre wrap="">lines, we very
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> much appreciate Cameron resuscitating the "Priorities for
</pre>
</blockquote>
</blockquote>
<pre wrap="">Conference
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Committee" thread, and anticipate chiming in over the coming
</pre>
</blockquote>
</blockquote>
<pre wrap="">weekend.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Indeed, the "starting from scratch" issues are something that are
resonating with our team.
Please let us know if you have any further questions, or need
clarifications on the points made above. We remain very hopeful
</pre>
</blockquote>
</blockquote>
<pre wrap="">that we can
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> receive Board approval *this week*. And, we are also hopeful that
</pre>
</blockquote>
</blockquote>
<pre wrap="">if we do
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> receive that approval it will be provided with some guidance on
</pre>
</blockquote>
</blockquote>
<pre wrap="">"what comes
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> next" in terms of putting signatures on the agreement and formally
initiating the financial request for an advance. The signatures
</pre>
</blockquote>
</blockquote>
<pre wrap="">part is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> most important as we continue to face a near term deadline for
</pre>
</blockquote>
</blockquote>
<pre wrap="">signing an
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> agreement with our venue that will legally secure the date.
Thanks in advance...
MT & the BLOC
On Tue, Mar 15, 2016 at 4:19 AM, Dirk Frigne <
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:dirk.frigne@geosparc.com">dirk.frigne@geosparc.com</a>>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Thank you Steven,
This is a clear statement and an improvement of the contract in
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">relation
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> to last year in relation to exposed risk.
i.m.h.o. this should pass the board's decision for this event. If
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> board should have still questions about the contract in general,
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">we
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> should discuss them and formulate an advise for improvement for
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">future
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> events.
One improvement could be that OSGeo get insured for the extra
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">exposed
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> risk (for future events), based on the financial history of all
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> FOSS4G events in the past.
Dirk.
On 14-03-16 16:39, Steven Feldman wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Venda, Board
The proposed agreement is identical to the one that OSGeo has
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">entered
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> into with Bonn for 2016, with the following variations:
</pre>
<blockquote type="cite">
<pre wrap=""> 1. The names
2. The seed funding is up to £70,000 not $57.500
3. The advance is for up to $45,000 not $57,500 (overall the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">total
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> exposure is the same as 2016 at $115,000)
</pre>
<blockquote type="cite">
<pre wrap=""> 4. The insertion of Mitigation, Indemnification and Arbitration
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">clauses
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> which I understand are standard clauses in US agreements of this
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">type and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> apply equally to both parties.
</pre>
<blockquote type="cite">
<pre wrap=""> The additional guarantee is intended to cover the very unlikely
</pre>
</blockquote>
<pre wrap=""> circumstance that the FOSS4G is financially unsuccessful. If the
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">event
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> loses money OSGeo is at risk of losing our seed money and an
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">additional
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> $45,000 up to a maximum exposure of $115,000. This agreement
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">limits our
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> exposure to $115,000 previously we had potentially unlimited
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">exposure.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> I hope this helps the board in considering this motion
Cheers
______
Steven
</pre>
<blockquote type="cite">
<pre wrap=""> On 14 Mar 2016, at 14:36, Venkatesh Raghavan <
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:venka.osgeo@gmail.com">venka.osgeo@gmail.com</a>>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Dear Micheal, Guido and all,
The agreement of seed funding was presented by Guido
at the Board meeting on 10 March, 2016 and the Board
members requested for further clarification especially
about the "additional guarantee".
Since all the board members are not following conference
mailing list, I would request that Micheal of Guido
to provide a brief summary of the request including
clarification on the "additional guarantee" and also
link to any relevant documents. This will help the
board members to get a clearer understanding and
facilitate to taking timely decision.
Thanks in advance.
Best
Venka
On 2016/03/10 2:51, Michael Terner wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Eli:
Thanks for the pointer to SVN, Guido is versed in these
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">technologies
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> will act as our "user" and POC on this (and you've seen he's
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">already
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> chimed
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> in to this effect). We will do our part to document our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">experiences and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> make everything available via SVN.
Also, apologies for the "FOSSGIS e.V." reference; we
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">understood what
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> it was
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and attempted to excise them all from "our version" of the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">document.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Apparently we missed one so thanks for the heads-up. As per
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">Steven's
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> note,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> his latest version with the lower "additional guarantee"
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">amount should
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> have
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> this corrected already.
Thanks again to all for your assistance on this.
MT
On Wed, Mar 9, 2016 at 12:30 PM, Guido Stein <
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:gstein@appgeo.com">gstein@appgeo.com</a>>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Hey Eli,
I would be happy to help with this.
Let me know the credentials and I will do my best to update
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">as we get
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> these official documents squared away.
-guido
On Wed, Mar 9, 2016 at 12:22 PM Eli Adam <
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:eadam@co.lincoln.or.us">eadam@co.lincoln.or.us</a>>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Hi Michael,
Are you or someone on the BLOC able to use svn? If so, I'd
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">like to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> give them access to <a class="moz-txt-link-freetext" href="http://svn.osgeo.org/osgeo/foss4g/">http://svn.osgeo.org/osgeo/foss4g/</a> so
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">that
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> things
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> like these documents can be stored there (at least once
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">finalized and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> approved).
"FOSSGIS e.V." is a German organization/corporation/nonprofit
associated with the FOSSGIS conference and Bonn LOC. They
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">are not a
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> party to this agreement and all mention of them should be
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">removed.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Please revised the documents accordingly.
Eli
On Wed, Mar 9, 2016 at 6:20 AM, Michael Terner <
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:mgt@appgeo.com">mgt@appgeo.com</a>>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Steven:
Thanks for keeping this moving and the good questions,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">suggestions
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> observations.
Board:
Thanks very much for taking this up on short notice. We
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">really
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> appreciate
</pre>
<blockquote type="cite">
<pre wrap=""> the attention.
To Steven's questions/suggestions:
YES, we are comfortable changing the "additional guarantee"
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> downward to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> match the Bonn "total value." Indeed, we were "connecting
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the dots"
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> based on
</pre>
<blockquote type="cite">
<pre wrap=""> the Bonn template, and had not completed a full risk
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">assessment.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Steven
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> makes a very good point that the "insurance policies" that
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">we can
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> pursue
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> after we have an agreement will help better quantify
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">"actual risk"
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> exposure. We are comfortable proceeding with what Steven
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">proposes
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> (i.e.,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> $115k max), and if we feel an alteration is
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">necessary/warranted
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> we'll
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> bring
</pre>
<blockquote type="cite">
<pre wrap=""> that back to conference dev at a later time. Indeed, our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">nearest
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> term
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> need
</pre>
<blockquote type="cite">
<pre wrap=""> is to formally enter into agreement so that we can secure
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">our venue
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> via
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> our
</pre>
<blockquote type="cite">
<pre wrap=""> PCO. So, YES, $115k (i.e., $70k advance, $45k "additional
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> guarantee") is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> good. Thank you.
YES, we appreciate your understanding and open mindedness
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">to the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> legal
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> clauses (thank you Darrell for the +1 on that). Ultimately,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">these
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> all
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> protect both OSGeo and the LOC/PCO and/or show a preference
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">for
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> non-litigious dispute resolution. Over time, these might be
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> considered
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> as
</pre>
<blockquote type="cite">
<pre wrap=""> additions to the "template agreement". And, we welcome
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">further
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> review/input
</pre>
<blockquote type="cite">
<pre wrap=""> from people familiar with contracts/agreements.
As Steven relays, our PCO reviewed and was comfortable with
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> agreement's
</pre>
<blockquote type="cite">
<pre wrap=""> existing language on guarantees. She only asked that the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">additional
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> clauses
</pre>
<blockquote type="cite">
<pre wrap=""> be added. And, as per above, if we perform a more detailed
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">risk
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> assessment
</pre>
<blockquote type="cite">
<pre wrap=""> it sounds like there is an avenue to re-approach Conf Dev on
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> increasing
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the
</pre>
<blockquote type="cite">
<pre wrap=""> guarantee.
Indeed, OSGeo's very good 10 year record of having strong
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> conferences
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> should
</pre>
<blockquote type="cite">
<pre wrap=""> help moderate insurance costs. And the BLOC has every
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">intention of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> extending
</pre>
<blockquote type="cite">
<pre wrap=""> that success with Boston.
Sincerely and with thanks...
MT & the BLOC
On Wed, Mar 9, 2016 at 7:24 AM, Steven Feldman <
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Michael
The additional guarantee for Bonn was based upon a risk
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">analysis at
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> different points in the build up to the conference and an
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">estimate
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> maximum exposure if the event had to be cancelled or
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">proceeded
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> with a
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> lower
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> than viable attendance. It was not automatically equal to
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the seed
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> funding.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> I don’t want to just negotiate you down to a lower figure.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">Can you
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> your PCO consider the exposure at different points and
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">come up
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> with a
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> revised additional guarantee that you need. If you will be
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> offsetting
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> any
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> additional risk through an insurance policy it might be
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">worth
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> exploring the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> premium versus excess ratios to come up with the most
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">efficient
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> balance
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> between an OSGeo additional guarantee and insurance.
In my motion to the CC I asked for approval for the seed
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">funds but
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> did
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> not
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> mention the ‘additional guarantee’. Given time pressures I
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">am
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> going to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> submit a proposal to the Board for consideration at
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">tomorrow
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> meeting
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> for
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> seed funds of $70k and an additional guarantee of up to
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">$45k i.e. a
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> total
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> exposure of $115k which is the same level of guarantee
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">offered to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Bonn
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> for
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> this year. If you come up with a different level of
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">additional
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> guarantee or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the CC objects I will have to go back to the board and ask
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">them to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> adapt the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> motion subsequently.
Darrell has suggested, in a separate mail in this thread,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">that the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> additional ‘legal’ paras are standard clauses, unless
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">someone else
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> objects I
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> am happy to forward the agreement (with additional
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">guarantee
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> amended)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> to the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> board for approval.
Darrell also raised the question of how OSGeo can limit
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">it’s
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> liability
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the event that the PCO or the LOC undertakes irrevocable
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> commitments in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> excess of the agreed sum. My understanding is that the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">agreement is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> primarily between OSGeo and the PCO with the LOC acting as
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">our
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> agent,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> PCO by signing this agreement accepts that OSGeo liability
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> limited
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> $115k (or whatever sum we agree) and will take necessary
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">steps
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> (i.e.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> insurance to mitigate any risks). While we there is some
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> uncertainty
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> about
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the enforceability of this agreement or its outcome, it is
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">a lot
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> better than
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> we had previously where nearly everything was done on the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">basis of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> a
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> ‘gentleman’s agreement’ - that said, so far no global
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">FOSS4G has
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> had
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> to call
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> on OSGeo to bail them out.
I have copied the Board into this mail so that they are
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">fully
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> aware of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> background and our discussions.
Cheers
______
Steven
On 8 Mar 2016, at 20:42, Michael Terner <a class="moz-txt-link-rfc2396E" href="mailto:mgt@appgeo.com"><mgt@appgeo.com></a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Totally fair questions. Here's where these things came
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">from:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Regarding the "advance" and the guarantee: We followed the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">form of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> how
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Bonn was setup. In the Bonn template "schedule" that was
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">shared
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> with us
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> there was $57,500 for the "advance" and $57,500 for the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">"additional
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> guarantee". Then the schedule identified $115,000 for the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">"Maximum
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> total
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> OSGeo financial exposure.". The previous threads had
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">identified
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> our
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> total
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> "maximum advance" as $70,000 (that we would seek in two
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> installments).
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Since
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the "additional guarantee" had not been discussed
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">explicitly I
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> followed the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> "Bonn model" and had the additional guarantee match the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">advance
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> payment,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> i.e., the $70,000; for a total exposure of $140,000. If
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">that's not
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> appropriate, or the "additional guarantee"; or "total
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">exposure"
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> needs
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> back down we will figure it out with your guidance.
Regarding the "legal" language: In reviewing the Bonn
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">agreement we
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> were
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> both pleased and a little surprised that there weren't
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">more "terms
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> conditions". We're all for simplicity and clarity. That
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">said, our
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> PCO,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Delaney Meeting & Event Management (DMEM) made these
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">suggestions as
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> they
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> will be a signatory to the agreement. In short, these are
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">common
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> sense
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> protections that are routine in almost all contracts. We
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">certainly
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> understand and respect your potential need to have
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">additional
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> review,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and we
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> certainly reviewed the language but did not feel that
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">engaging
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> legal
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> counsel
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> was necessary due to the fact that these clauses are so
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">commonplace
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> (i.e., I
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> have seen this language many times before) and because
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">they protect
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> both
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> parties to the agreement. Here's my layman's summary of
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">what they
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> mean
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> why they are important (and this is in no way is designed
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> dissuade
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> you
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> from getting the reviews OSGeo thinks are necessary):
Mitigation Clause/Force Majeure: If something terrible and
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">beyond
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> control of either of us happens (e.g., crazy weather;
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">terrorism
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> that
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> locks
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> down travel; etc.) that causes the event to be cancelled
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">late in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> game,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> there is a means to do that. As per later in the document,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">we will
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> have
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> "cancellation insurance" so that if this happens neither
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">party
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> loses
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> already
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> spent $'s.
Indemnification: Is a mutual protection that if either
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">party is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> acting
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> bad faith or shows negligence or blatant incompetence,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">that causes
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> damage
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and as a result the other party (i.e., the one that did
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">not cause
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> problem) is sued, the party at fault is responsible for
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">those
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> damages
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> must indemnify the non-responsible party.
Arbitration: If there is a dispute, this clause indicates
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">that it
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> will
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> be
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> resolved through arbitration, as opposed to a lawsuit.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">Arbitration
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> generally a quicker and less costly process (at least in
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the USA).
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Event insurance: We will obtain insurance to cover both
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> cancellation
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> exposure and liability that may result from this event.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">This is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> commonplace
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and our PCO is familiar with these types of policies and
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">affordable
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> means of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> obtaining them. These costs are included in our budget.
Even with these additions, this agreement remains very
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">lean.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Obviously, we
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> do not want to add unnecessary complexity or slow things
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">down.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Rather,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> our
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> intent is to have a solid agreement that protects both
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">parties and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> helps to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> cement a productive and collaborative partnership.
Please let us know if there's any other information you
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">require; or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> anything else we can do to clarify things. If this needs
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">more
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> thorough
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> time consuming review we regret that, but also accept it.
Please let us know what comes next, and in particular
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">whether we
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> should
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> revise our request for the size of the "additional
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">guarantee".
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Thanks to all for the work you're putting into this...
MT
On Tue, Mar 8, 2016 at 3:04 PM, Steven Feldman <
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> <a class="moz-txt-link-abbreviated" href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Michael
The overall guarantee including seed funding is $140k - I
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">do not
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> recall
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> this high a number being advised previously. Could you
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">clarify.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
While I do not have any fundamental disagreement with the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">clauses
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> that
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> you have added at the end, they will need to be reviewed
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">by
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> someone
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> more
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> legally qualified than me which may incur both costs and
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">delay.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> ______
Steven
On 8 Mar 2016, at 16:43, Michael Terner <a class="moz-txt-link-rfc2396E" href="mailto:mgt@appgeo.com"><mgt@appgeo.com></a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Conference Dev Committee:
Thank you very much for your support of the motion to
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">provide our
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> team
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> seed funding.
As promised earlier in the thread, attached is a "draft
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">agreement"
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> between OSGeo and the Boston Location Organizing Committee
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> (BLOC), as
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> well
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> as with our PCO, Delaney Meeting & Event Management
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">(DMEM). We are
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> hopeful
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> that this is on target and can be passed on to the Board
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">in time
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> for
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> their
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> meeting on Thursday. We are assuming that Conference Dev
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">will
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> bring
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> this to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the Board's attention.
Here's what you will find in the attached document
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">(attached as
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> .DOC,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> .ODT and .PDF):
Our re-work of the Bonn Template Agreement to include our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">specific
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> requests for advance and guarantees; as well as our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">"percentage of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> profits
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> returned to OSGeo" language that was also contained in our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> proposal
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> (and is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> slightly different than 90%).
Some common-sense legal terms that were suggested by DMEM
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">for
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> things
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> like
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Force Majeur, mutual indemnification and arbitration of
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">disputes.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> We
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> also
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> affirm our commitment to purchase our own cancellation and
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> liability
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> insurance.
Attachment 1 which is structured as a PCO contract
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">between OSGeo
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> DMEM
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> on behalf of the BLOC, allowing DMEM to serve as our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">financial
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> agent
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and as
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> the entity that would sign the commitment with our venue
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">(this was
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> distributed earlier).
Given the nature of this arrangement we have three
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">signature
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> lines for
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> OSGeo, the BLOC, and also DMEM, on behalf of the BLOC.
Please let us know if you have any question, or need
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">anything
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> further.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> And again, thanks in advance for carrying this forward to
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Board.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Sincerely,
MT & the BLOC
This e-mail message and any attachments may contain
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">confidential
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> legally privileged information. If you are not an intended
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> recipient
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> otherwise authorized to receive this message, you should
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">not use,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> copy,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> distribute, disclose or take any action based on the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">information
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> contained
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> in this e-mail or any attachments. If you have received
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">this
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> message
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> material in error, please advise the sender immediately
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">by reply
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> e-mail and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> delete this message. Thank you on behalf of Applied
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">Geographics,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Inc.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> (AppGeo).<OSGeo + BostonLOC Agreement DRAFT v3.odt><OSGeo
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">+
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> BostonLOC
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Agreement DRAFT v3.pdf><OSGeo + BostonLOC Agreement DRAFT
v3.doc>_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.orghttp://">Conference_dev@lists.osgeo.orghttp://</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">lists.osgeo.org/mailman/listinfo/conference_dev
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> --
Michael Terner
Executive Vice President
617-447-2468 Direct | 617-447-2400 Main
Applied Geographics, Inc.
24 School Street, Suite 500
Boston, MA 02108
<a class="moz-txt-link-abbreviated" href="http://www.AppGeo.com">www.AppGeo.com</a>
Please come to Boston for Global FOSS4G 2017:
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> <a class="moz-txt-link-freetext" href="http://2017.foss4g.org/">http://2017.foss4g.org/</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> This e-mail message and any attachments may contain
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">confidential or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> legally privileged information. If you are not an intended
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> recipient or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> otherwise authorized to receive this message, you should
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">not use,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> copy,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> distribute, disclose or take any action based on the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">information
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> contained
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> in this e-mail or any attachments. If you have received
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">this
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> message
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> material in error, please advise the sender immediately by
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">reply
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> e-mail and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> delete this message. Thank you on behalf of Applied
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">Geographics,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Inc.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> (AppGeo).
</pre>
</blockquote>
<pre wrap=""> --
Michael Terner
Executive Vice President
617-447-2468 Direct | 617-447-2400 Main
Applied Geographics, Inc.
24 School Street, Suite 500
Boston, MA 02108
<a class="moz-txt-link-abbreviated" href="http://www.AppGeo.com">www.AppGeo.com</a>
Please come to Boston for Global FOSS4G 2017:
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""> <a class="moz-txt-link-freetext" href="http://2017.foss4g.org/">http://2017.foss4g.org/</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> This e-mail message and any attachments may contain
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">confidential or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> legally
</pre>
<blockquote type="cite">
<pre wrap=""> privileged information. If you are not an intended
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">recipient or
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> otherwise
</pre>
<blockquote type="cite">
<pre wrap=""> authorized to receive this message, you should not use,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">copy,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> distribute,
</pre>
<blockquote type="cite">
<pre wrap=""> disclose or take any action based on the information
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">contained in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> this
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> e-mail or any attachments. If you have received this
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">message and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> material in
</pre>
<blockquote type="cite">
<pre wrap=""> error, please advise the sender immediately by reply e-mail
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> delete
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> this
</pre>
<blockquote type="cite">
<pre wrap=""> message. Thank you on behalf of Applied Geographics, Inc.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">(AppGeo).
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.orghttp://">Conference_dev@lists.osgeo.orghttp://</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">lists.osgeo.org/mailman/listinfo/conference_dev
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.orghttp://">Conference_dev@lists.osgeo.orghttp://</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">lists.osgeo.org/mailman/listinfo/conference_dev
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> _______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.orghttp://">Conference_dev@lists.osgeo.orghttp://</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">lists.osgeo.org/mailman/listinfo/conference_dev
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> _______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.orghttp://">Board@lists.osgeo.orghttp://</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">lists.osgeo.org/mailman/listinfo/board
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> --
Yours sincerely,
ir. Dirk Frigne
CEO @geosparc
Geosparc n.v.
Brugsesteenweg 587
B-9030 Ghent
Tel: +32 9 236 60 18
GSM: +32 495 508 799
<a class="moz-txt-link-freetext" href="http://www.geomajas.orghttp://www.geosparc.com">http://www.geomajas.orghttp://www.geosparc.com</a>
@DFrigne
be.linkedin.com/in/frigne
_______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.orghttp://">Board@lists.osgeo.orghttp://</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">lists.osgeo.org/mailman/listinfo/board
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
_______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/board">Board@lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/board</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________ Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:Board@lists.osgeo.org"><mailto:Board@lists.osgeo.org></a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a>
_______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a>
</pre>
</blockquote>
<pre wrap="">
--
Yours sincerely,
ir. Dirk Frigne
CEO @geosparc
Geosparc n.v.
Brugsesteenweg 587
B-9030 Ghent
Tel: +32 9 236 60 18
GSM: +32 495 508 799
<a class="moz-txt-link-freetext" href="http://www.geomajas.org">http://www.geomajas.org</a>
<a class="moz-txt-link-freetext" href="http://www.geosparc.com">http://www.geosparc.com</a>
@DFrigne
be.linkedin.com/in/frigne
_______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a>
</pre>
</blockquote>
<pre wrap="">
--
*Massimiliano Cannata*
Professore SUPSI in ingegneria Geomatica
Responsabile settore Geomatica
Istituto scienze della Terra
Dipartimento ambiente costruzione e design
Scuola universitaria professionale della Svizzera italiana
Campus Trevano, CH - 6952 Canobbio
Tel. +41 (0)58 666 62 14
Fax +41 (0)58 666 62 09
<a class="moz-txt-link-abbreviated" href="mailto:massimiliano.cannata@supsi.ch">massimiliano.cannata@supsi.ch</a>
*www.supsi.ch/ist <a class="moz-txt-link-rfc2396E" href="http://www.supsi.ch/ist"><http://www.supsi.ch/ist></a>*
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a></pre>
</blockquote>
<br>
</body>
</html>