<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Jeff,</p>
<p>Re sharing questions with the list, we don't need to require
people to subscribe to the list, we just need to be mindful that
we don't share private emails publicly. Probably the easiest way
to achieve this is to ask a person's permission before responding
publicly.<br>
</p>
<br>
<div class="moz-cite-prefix">On 19/01/2017 6:35 AM, Jody Garnett
wrote:<br>
</div>
<blockquote
cite="mid:CAOhbgAmkhiJDK5bMmfc5Kx25siVRRT-mSME83Le01iwvOQuyGQ@mail.gmail.com"
type="cite">
<div dir="ltr">I was going to add Q&A/Clarifications to the
website page. I think you already fielded some questions did you
not Jeff?</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>--</div>
<div>Jody Garnett</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On 18 January 2017 at 11:22, Jeffrey
Johnson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ortelius@gmail.com" target="_blank">ortelius@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">+1 on all
these. It may be a bit much to ask folks to subscribe to our<br>
list, does it allow through public posts, or could we
moderate those<br>
through and respond cc'ng the original person but keeping
the response<br>
on the list? Wiki is a great idea too.<br>
<br>
I concur that the project management overhead on our side is
probably<br>
not worth it, lets see what kind of questions/responses we
get.<br>
<div class="HOEnZb">
<div class="h5"><br>
On Wed, Jan 18, 2017 at 11:14 AM, Cameron Shorter<br>
<<a moz-do-not-send="true"
href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>>
wrote:<br>
> If we decide to answer questions publicly (which I
think we should), then I<br>
> also suggest that we encourage vendors to send
questions to this public<br>
> marketing email list.<br>
><br>
> Re question about breaking project up, I'd suggest
we aim to minimise OSGeo<br>
> volunteer workload and risk by encouraging bidders
to team up under one<br>
> prime rather than put in multiple bids for multiple
components.<br>
><br>
> Adding a wiki with questions and official responses
is probably a good idea<br>
> too.<br>
><br>
><br>
><br>
> On 18/01/2017 6:35 AM, Jeffrey Johnson wrote:<br>
>><br>
>> On Tue, Jan 17, 2017 at 11:28 AM, Jody Garnett
<<a moz-do-not-send="true"
href="mailto:jody.garnett@gmail.com">jody.garnett@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> On 17 January 2017 at 11:14, Jeffrey
Johnson <<a moz-do-not-send="true"
href="mailto:ortelius@gmail.com">ortelius@gmail.com</a>>
wrote:<br>
>>>><br>
>>>> One question I have had already is how
are we going to respond to<br>
>>>> questions from potential vendors.
Should they send them to<br>
>>>> <a moz-do-not-send="true"
href="mailto:secretary@osgeo.org">secretary@osgeo.org</a>
to be forwarded to us?<br>
>>><br>
>>><br>
>>> I assume so; you may wish to volunteer act
as point for the EOI process.<br>
>>> If<br>
>>> I remember our meeting notes Marc and I are
digging into policy/strategy<br>
>>> document.<br>
>><br>
>> Im happy to be the POC, but I do NOT want
people emailing me directly<br>
>> with these questions and prefer to answer them
formally. Perhaps we<br>
>> ask the secretary to prepare any questions and
send them to us and we<br>
>> can respond as a group formally and with a
public record (even if I am<br>
>> taking the lead)<br>
>><br>
>>>> The question at hand was whether we
would consider splitting up the<br>
>>>> contract so that a firm was only
proposing for one or two parts and we<br>
>>>> would have another vendor for the other
component(s). I think this<br>
>>>> could be ok, but would require more
project management on our side.<br>
>>>> Should we put language to this effect
in the letter to discuss?<br>
>>><br>
>>><br>
>>> I see.<br>
>>><br>
>>> The update to splitting out content
migration is it could dovetail into<br>
>>> an<br>
>>> going editing role in 2018.<br>
>>><br>
>>>> Really hoping we can get this out
today, the clock is ticking :)<br>
>>><br>
>>><br>
>>> Can we send it, and answer questions as
they come in. You can add Q&A to<br>
>>> the<br>
>>> <a moz-do-not-send="true"
href="http://www.osgeo.org/marketing/rebranding.html"
rel="noreferrer" target="_blank">http://www.osgeo.org/<wbr>marketing/rebranding.html</a>
page.<br>
>><br>
>> Marc, I'd prefer you send this to discuss as
the chair of our committee.<br>
>> ______________________________<wbr>_________________<br>
>> Marketing mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:Marketing@lists.osgeo.org">Marketing@lists.osgeo.org</a><br>
>> <a moz-do-not-send="true"
href="https://lists.osgeo.org/mailman/listinfo/marketing"
rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/marketing</a><br>
><br>
><br>
> --<br>
> Cameron Shorter<br>
> M <a moz-do-not-send="true"
href="tel:%2B61%20419%20142%20254"
value="+61419142254">+61 419 142 254</a><br>
><br>
> ______________________________<wbr>_________________<br>
> Marketing mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Marketing@lists.osgeo.org">Marketing@lists.osgeo.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.osgeo.org/mailman/listinfo/marketing"
rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/marketing</a><br>
______________________________<wbr>_________________<br>
Marketing mailing list<br>
<a moz-do-not-send="true"
href="mailto:Marketing@lists.osgeo.org">Marketing@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="https://lists.osgeo.org/mailman/listinfo/marketing"
rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/marketing</a></div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
M +61 419 142 254</pre>
</body>
</html>