[OSGeo-Conf] [Board] On the creation of permanent OSGeo/FOSS4G CRM

Cameron Shorter cameron.shorter at gmail.com
Thu Mar 27 14:28:36 PDT 2014

+1 from me too, with the following comments:

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: 

2. When setting up the infrastructure, I suggest ensuring that it is 
sustainable long term, with very little maintenance.

3. In particular, use the Open Source version rather than commercial 
version of Sugar CRM, so we are not dependant on fees.

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.

On 28/03/2014 7:52 AM, David William Bitner wrote:
> Big +1.
> On Thu, Mar 27, 2014 at 3:50 PM, Darrell Fuhriman <darrell at garnix.org 
> <mailto:darrell at garnix.org>> wrote:
>     One of things that has become apparent in going through the
>     process of getting sponsorships for FOSS4G is that the current
>     system is rather unwieldy. In fact, the use of the word "system"
>     implies a type of order which does not exist.
>     There are no designated contacts at each company, no consistent
>     tracking of past sponsorships or expressions of interest, no
>     tracking of non-functioning e-mails, or people who have left a
>     company.
>     In short, it's a complete fucking disaster.
>     This is a problem because:
>     1) FOSS4G is dependent on sponsorships to finish in the black
>     2) OSGeo is dependent on FOSS4G events (not just the big annual
>     conference) for a large portion of its income
>     3) We should be making it easy, not hard, to keep FOSS4G/OSGeo
>     solvent.
>     We have individuals who have expressed an interest in getting all
>     of the past and current data into a CRM so we can more easily
>     track this in the future. However, unless there is a future for
>     such a system, it's probably not worth the non-trivial amount of
>     effort it would take.
>     Hence, I propose:
>     The 2014 LOC will work to configure an instance of SugarCRM,
>     including entering the data we have collected on current and past
>     sponsorships.
>     After the conclusion of FOSS4G 2014, OSGeo would agree to:
>     1) Move the SugarCRM instance to be hosted and maintained by OSGeo
>     2) Strongly encourage (mandate?) its use by future OSGeo
>     affiliated conferences
>     3) Give access to other geospatial related events as appropriate
>     I realize there is some reluctance to "give orders" to the people
>     who have volunteered to do these events. However in the long run
>     having a central CRM will /reduce/ the amount of work required by
>     future LOCs, and by past ones who get requests to dig out contact
>     information from events that occurred years ago.
>     The use of a CRM could also be expanded to track contact
>     information for all attendees including which events they've
>     attended, so they can be contacted about future relevant events --
>     another case where there is no coordination or sanity to any of
>     the extant data.
>     Thoughts?
>     Darrell
>     _______________________________________________
>     Board mailing list
>     Board at lists.osgeo.org <mailto:Board at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/board
> -- 
> ************************************
> David William Bitner
> dbSpatial LLC
> 612-424-9932
> _______________________________________________
> Conference_dev mailing list
> Conference_dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/conference_dev

Cameron Shorter,
Software and Data Solutions Manager
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009

P +61 2 9009 5000,  W www.lisasoft.com,  F +61 2 9009 5099

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20140328/5683eaca/attachment.html>

More information about the Conference_dev mailing list