<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Darrell,<br>
I think you are getting a rough consensus on this topic.<br>
I suggest writing a draft section in the foss4g cookbook, following
writing guide here:<br>
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/FOSS4G_Handbook#Section_Writing_Guide">http://wiki.osgeo.org/wiki/FOSS4G_Handbook#Section_Writing_Guide</a><br>
<br>
Once done, give people a chance to review and adjust words.<br>
Then we can vote to have the section added.<br>
<br>
Darrell,<br>
I'm expecting (hoping) that this is the first of many good ideas
that you will have as you progress through the process of running
foss4g, and I strongly encourage you to add new draft sections to
the cookbook as you go. I find it is much easier to write as you
are doing it, rather than to retrospectively add ideas.<br>
<br>
<div class="moz-cite-prefix">On 28/03/14 6:51 PM, Bart van den
Eijnden wrote:<br>
</div>
<blockquote cite="mid:8F5100E2-4ECB-4065-8E80-18F5C2B6A533@osgis.nl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Personally I think it would be fine to mandate this is in the RFP
document.
<div><br>
</div>
<div>Thanks for taking the lead on this Darrell.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Bart</div>
<div><br>
<div>
<div>On 28 Mar 2014, at 00:06, Darrell Fuhriman <<a
moz-do-not-send="true" href="mailto:darrell@garnix.org">darrell@garnix.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;">
<div><br>
</div>
<div>1) I agree that it belongs in the handbook. I’d like
it to be stronger than just a suggestion, however. I’d
like to be the default assumption. It’s true that the
idea is compelling enough on its own to make it likely
people would use it, but… to be blunt, we have enough to
do, so if we’re going to expend the substantial amount
of work required to make this happen, we’d like to be
confident that it won’t die after September.</div>
<div><br>
</div>
<div>2,3) There’s no such thing as software without
maintenance, so if OSGeo isn't willing to commit to
doing the maintenance, then I’d suggest that a
commercially hosted CRM is a wise investment. For
example, a single SugarCRM user is $35/mo. That is a
very modest expense, given the return on investment,
even at half-a-dozen users (1-2 per FOSS4G conference).</div>
<div><br>
</div>
<div>4) Boy howdy, do we. In general I think organizers
have adopted a pretty conservative approach, but having
an overarching OSGeo policy that was a mandatory
umbrella for all conferences is a <i>much</i> better
idea.</div>
<div><br>
</div>
<div>Darrell</div>
<div><br>
</div>
<div><br>
<div>
<div>On Mar 27, 2014, at 14:28, Cameron Shorter <<a
moz-do-not-send="true"
href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Darrell,<br>
+1 from me too, with the following comments:<br>
<br>
1. I think the best way to set this up, and
ensure that it will continue to be used at
future conferences is to collect this
suggestion, along with others, into the emerging
FOSS4G Cookbook: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://wiki.osgeo.org/wiki/FOSS4G_Handbook">http://wiki.osgeo.org/wiki/FOSS4G_Handbook</a><br>
<br>
2. When setting up the infrastructure, I suggest
ensuring that it is sustainable long term, with
very little maintenance.<br>
<br>
3. In particular, use the Open Source version
rather than commercial version of Sugar CRM, so
we are not dependant on fees.<br>
<br>
4. We need a policy in place regarding privacy
of data. People and organisations need to know
how widely their contact details are being
shared before they hand them over. <br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
_______________________________________________<br>
Conference_dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>