<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div><div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">----</font></font></div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Michael Smith</font></font></div><div><div>OSGeo Foundation Treasurer</div><div><a href="mailto:treasurer@osgeo.org">treasurer@osgeo.org</a></div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Board <<a href="mailto:board-bounces@lists.osgeo.org">board-bounces@lists.osgeo.org</a>> on behalf of Venkatesh Raghavan <<a href="mailto:raghavan@media.osaka-cu.ac.jp">raghavan@media.osaka-cu.ac.jp</a>><br><span style="font-weight:bold">Date: </span> Tuesday, March 15, 2016 at 7:47 PM<br><span style="font-weight:bold">To: </span> OSGeo Board <<a href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [Board] [OSGeo-Conf] 2017 Boston agreement & seed funding - IMPORTANT<br></div><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear Board,<br>
<br>
<blockquote type="cite">MOT7: Seek additional clarifications and
attend to this agenda item by e-mail within 7 working days
</blockquote>
<br>
Pending the approval of the above motion moved at<br>
the Board meeting held on 10 March, I would like to<br>
remind that we have two working days remaining<br>
to seek further clarification concerning the<br>
2017 Boston agreement & seed funding request and<br>
vote for board approval.<br>
<br>
Considering the time available and also the fact that I<br>
do not intend to seek further clarification from my side,<br>
I would like to move the motion to approve the request<br>
from BLOC.</div></div></div></blockquote></span><div><br></div><div>+1 to approve request for FOSS4G 2017</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div bgcolor="#FFFFFF" text="#000000"><div class="moz-cite-prefix"><br>
<br>
Best<br>
<br>
Venka<br>
<br>
<br>
<br>
<br>
On 2016/03/15 21:17, Michael Terner wrote:<br>
</div>
<blockquote cite="mid:CAEFvZu4O-MGHqd6Ls+sOmvv7HRHQP7wyPx=bMqU5WEKMymh9Zg@mail.gmail.com" type="cite">
<pre wrap="">Venka:
Thanks for the fair questions and thanks to the board for the serious
consideration of our request.
Steven, thanks for the general outline of a response and an enumeration of
our request. Your four points are entirely accurate and indeed several
people guided us to examine the Bonn agreement as a template for an
OSGeo/LOC agreement. This is precisely what we did, although in our case,
and unlike Bonn, the BLOC is not a legal entity and thus as with some past
conferences our PCO is part of the agreement as our "financial agent". So
here are a few additional details on the four main points:
1. *Names*: Our agreement has three parties: OSGeo, the Boston Location
Organizing Committee (BLOC) and Delaney Meeting & Event Management, our
PCO, who is acting as our financial agent.
2. *Seed funding*: We are asking for approval of up to maximum of
$70,000 of advances. As per the email threads, we anticipate doing this
through two separate requests. The first would be for $20,000 +/-
immediately following our hoped for approval of the agreement. The second
would be for the remaining $50,000 after the Bonn Conference concludes and
as we begin to ramp up at a faster pace (and as deposits come due).
3. *Additional guarantee*: Again, we followed the Bonn agreement model,
and as Steven points out the "total exposure" for OSGeo between the
advances and additional guarantee are the same for both Boston and Bonn. I
would also observe that the known precedent of OSGeo providing these
guarantees was something we considered strongly in forming our bid. Indeed,
both the BLOC and OSGeo are "in this together" with substantial "skin in
the game" and we are both strongly motivated for a superior and financially
successful event. We will work tirelessly to ensure Boston continues the
FOSS4G streak of being financially successful.
4. *Contractual clauses*: As has happened over the years, we would
certainly urge OSGeo to continue building on the template agreement and
these clauses provide important *mutual *protections as well as
providing a framework for cost-effective dispute resolution in the unlikely
event it is needed. They are standard clauses, but they also articulate
important principles.
Last, please consider the BLOC to have a strong +1 to Dirk's suggestion
that OSGeo look at an insurance approach for FOSS4G that could be designed
to cover future events and could leverage the good financial record of past
FOSS4G's. This would be one more thing that the "next conference" (e.g.,
2018) would not have to start from scratch with. Along those lines, we very
much appreciate Cameron resuscitating the "Priorities for Conference
Committee" thread, and anticipate chiming in over the coming weekend.
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 that we can
receive Board approval *this week*. And, we are also hopeful that if we do
receive that approval it will be provided with some guidance on "what comes
next" in terms of putting signatures on the agreement and formally
initiating the financial request for an advance. The signatures part is
most important as we continue to face a near term deadline for signing an
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 <a class="moz-txt-link-rfc2396E" href="mailto:dirk.frigne@geosparc.com"><dirk.frigne@geosparc.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thank you Steven,
This is a clear statement and an improvement of the contract in relation
to last year in relation to exposed risk.
i.m.h.o. this should pass the board's decision for this event. If the
board should have still questions about the contract in general, we
should discuss them and formulate an advise for improvement for future
events.
One improvement could be that OSGeo get insured for the extra exposed
risk (for future events), based on the financial history of all the
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 entered
</pre>
</blockquote>
<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 total
</pre>
</blockquote>
<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 clauses
</pre>
</blockquote>
<pre wrap="">which I understand are standard clauses in US agreements of this type and
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 event
loses money OSGeo is at risk of losing our seed money and an additional
$45,000 up to a maximum exposure of $115,000. This agreement limits our
exposure to $115,000 previously we had potentially unlimited exposure.
</pre>
<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 <a class="moz-txt-link-rfc2396E" href="mailto:venka.osgeo@gmail.com"><venka.osgeo@gmail.com></a></pre>
</blockquote>
</blockquote>
<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 technologies
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 already
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 experiences and
make everything available via SVN.
Also, apologies for the "FOSSGIS e.V." reference; we understood what
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 document.
Apparently we missed one so thanks for the heads-up. As per Steven's
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">note,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">his latest version with the lower "additional guarantee" amount should
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 <a class="moz-txt-link-rfc2396E" href="mailto:gstein@appgeo.com"><gstein@appgeo.com></a></pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""></pre>
<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 as we get
these official documents squared away.
-guido
On Wed, Mar 9, 2016 at 12:22 PM Eli Adam <a class="moz-txt-link-rfc2396E" href="mailto:eadam@co.lincoln.or.us"><eadam@co.lincoln.or.us></a></pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">Hi Michael,
Are you or someone on the BLOC able to use svn? If so, I'd like to
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 that
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 finalized and
approved).
"FOSSGIS e.V." is a German organization/corporation/nonprofit
associated with the FOSSGIS conference and Bonn LOC. They are not a
party to this agreement and all mention of them should be removed.
Please revised the documents accordingly.
Eli
On Wed, Mar 9, 2016 at 6:20 AM, Michael Terner <a class="moz-txt-link-rfc2396E" href="mailto:mgt@appgeo.com"><mgt@appgeo.com></a></pre>
</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">
<pre wrap="">Steven:
Thanks for keeping this moving and the good questions, suggestions
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 really
</pre>
</blockquote>
<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 the dots"
</pre>
</blockquote>
<pre wrap="">based on
</pre>
<blockquote type="cite">
<pre wrap="">the Bonn template, and had not completed a full risk assessment.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 we can
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 "actual risk"
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 proposes
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 necessary/warranted
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 nearest
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 our venue
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 to the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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, these
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 for
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 further
</pre>
</blockquote>
<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 the
</pre>
</blockquote>
<pre wrap="">agreement's
</pre>
<blockquote type="cite">
<pre wrap="">existing language on guarantees. She only asked that the additional
</pre>
</blockquote>
<pre wrap="">clauses
</pre>
<blockquote type="cite">
<pre wrap="">be added. And, as per above, if we perform a more detailed risk
</pre>
</blockquote>
<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 intention of
</pre>
</blockquote>
<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 <<a class="moz-txt-link-abbreviated" href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a></pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""></pre>
<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 analysis at
different points in the build up to the conference and an estimate
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 proceeded
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 the seed
</pre>
</blockquote>
</blockquote>
<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. Can you
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 come up
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 worth
</pre>
</blockquote>
</blockquote>
<pre wrap="">exploring the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">premium versus excess ratios to come up with the most efficient
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 funds but
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 am
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 tomorrow
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 $45k i.e. a
</pre>
</blockquote>
</blockquote>
<pre wrap="">total
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">exposure of $115k which is the same level of guarantee offered to
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 additional
</pre>
</blockquote>
</blockquote>
<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 them to
</pre>
</blockquote>
</blockquote>
<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, that the
additional ‘legal’ paras are standard clauses, unless someone else
</pre>
</blockquote>
</blockquote>
<pre wrap="">objects I
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">am happy to forward the agreement (with additional guarantee
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 it’s
</pre>
</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">
<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 agreement is
primarily between OSGeo and the PCO with the LOC acting as our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 is
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 steps
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 a lot
</pre>
</blockquote>
</blockquote>
<pre wrap="">better than
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">we had previously where nearly everything was done on the basis of
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 FOSS4G has
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 fully
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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> wrote:
Totally fair questions. Here's where these things came from:
Regarding the "advance" and the guarantee: We followed the form of
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 shared
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 "additional
guarantee". Then the schedule identified $115,000 for the "Maximum
</pre>
</blockquote>
</blockquote>
<pre wrap="">total
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">OSGeo financial exposure.". The previous threads had identified
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 explicitly I
</pre>
</blockquote>
</blockquote>
<pre wrap="">followed the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">"Bonn model" and had the additional guarantee match the advance
</pre>
</blockquote>
</blockquote>
<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 that's not
appropriate, or the "additional guarantee"; or "total exposure"
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 agreement we
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 more "terms
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 said, our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 suggestions as
</pre>
</blockquote>
</blockquote>
<pre wrap="">they
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">will be a signatory to the agreement. In short, these are common
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 certainly
understand and respect your potential need to have additional
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 engaging
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 commonplace
</pre>
</blockquote>
</blockquote>
<pre wrap="">(i.e., I
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">have seen this language many times before) and because they protect
</pre>
</blockquote>
</blockquote>
<pre wrap="">both
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">parties to the agreement. Here's my layman's summary of what they
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 to
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 beyond
</pre>
</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">
<pre wrap="">control of either of us happens (e.g., crazy weather; terrorism
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 late in
</pre>
</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">
<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, we will
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 party
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 party is
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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, that causes
</pre>
</blockquote>
</blockquote>
<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 not cause
</pre>
</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">
<pre wrap="">problem) is sued, the party at fault is responsible for those
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 that it
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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. Arbitration
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 the USA).
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. This is
</pre>
</blockquote>
</blockquote>
<pre wrap="">commonplace
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">and our PCO is familiar with these types of policies and affordable
</pre>
</blockquote>
</blockquote>
<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 lean.
</pre>
</blockquote>
</blockquote>
<pre wrap="">Obviously, we
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">do not want to add unnecessary complexity or slow things down.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 parties and
</pre>
</blockquote>
</blockquote>
<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 require; or
anything else we can do to clarify things. If this needs more
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 whether we
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 guarantee".
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 do not
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">recall
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">this high a number being advised previously. Could you clarify.
While I do not have any fundamental disagreement with the clauses
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 by
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 delay.
______
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> wrote:
Conference Dev Committee:
Thank you very much for your support of the motion to provide our
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 agreement"
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 (DMEM). We are
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 in time
</pre>
</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">
<pre wrap="">their
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">meeting on Thursday. We are assuming that Conference Dev will
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 (attached as
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 specific
requests for advance and guarantees; as well as our "percentage of
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 for
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 disputes.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 between OSGeo
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 financial
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 (this was
distributed earlier).
Given the nature of this arrangement we have three signature
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 anything
</pre>
</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="">And again, thanks in advance for carrying this forward to the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 confidential
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 not use,
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">copy,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">distribute, disclose or take any action based on the information
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 this
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 by reply
</pre>
</blockquote>
</blockquote>
</blockquote>
<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 Geographics,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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>
<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.org">Conference_dev@lists.osgeo.org</a><a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></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>
</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 confidential or
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 not use,
</pre>
</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">
<pre wrap="">distribute, disclose or take any action based on the information
</pre>
</blockquote>
</blockquote>
<pre wrap="">contained
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">in this e-mail or any attachments. If you have received this
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 reply
</pre>
</blockquote>
</blockquote>
<pre wrap="">e-mail and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">delete this message. Thank you on behalf of Applied Geographics,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 confidential or
</pre>
</blockquote>
<pre wrap="">legally
</pre>
<blockquote type="cite">
<pre wrap="">privileged information. If you are not an intended recipient or
</pre>
</blockquote>
<pre wrap="">otherwise
</pre>
<blockquote type="cite">
<pre wrap="">authorized to receive this message, you should not use, copy,
</pre>
</blockquote>
<pre wrap="">distribute,
</pre>
<blockquote type="cite">
<pre wrap="">disclose or take any action based on the information contained in
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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 message and
</pre>
</blockquote>
<pre wrap="">material in
</pre>
<blockquote type="cite">
<pre wrap="">error, please advise the sender immediately by reply e-mail and
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<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. (AppGeo).
_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></pre>
</blockquote>
<pre wrap=""></pre>
</blockquote>
<pre wrap=""></pre>
</blockquote>
<pre wrap="">
_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></pre>
</blockquote>
<pre wrap="">_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</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-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=""></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>
</div></div>
_______________________________________________
Board mailing list
<a href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a></blockquote></span></body></html>