shfeldman at gmail.com
Thu Jun 18 09:12:55 PDT 2015
Be careful here. Either the LOC takes responsibility for a loss or OSGeo does, you can’t qualify with “if the LOC does something negligent …”
If OSGeo is going to take the financial responsibility for a FOSS4G then it may need to be the signatory on all contracts and at a minimum it would need a financial rep on the LOC with some authority. Gets messy.
I think the financial/contractual relationship between the LOC and OSGeo has always been a ‘grey’ area. Fortunately, so far, we have muddled through very successfully. The costs and commitments for a large FOSS4G are substantial (in 2013 our total spend was ca $600k although much was directly linked to attendance numbers) - it is not inconceivable that an event that failed to attract sponsorship and had below target attendance could lose $100-150k, that would be a big dent in the bank account.
Food for thought
> On 18 Jun 2015, at 16:29, Bart van den Eijnden <bartvde at osgis.nl> wrote:
> I fully agree.
> I think we should relief the financial stress from the Korea LOC.
> Of course given the theoretical case where an LOC would make a mess of things, we should not be liable ideally, but in the South-Korea case they are giving their full best and even more IMHO.
> Does anyone have background on why this was chosen before? I can’t recall the discussions.
> Best regards,
>> On 18 Jun 2015, at 17:25, Darrell Fuhriman <darrell at garnix.org <mailto:darrell at garnix.org>> wrote:
>> That is, to be blunt, absurd.
>> If OSGeo is getting the benefits of any proceeds, they need to be assuming the liability as well.
>>> On Jun 18, 2015, at 08:20, 신상희 <shshin at gaia3d.com <mailto:shshin at gaia3d.com>> wrote:
>>> Hi all,
>>> Currently all liability will be upon Seoul LOC not OSGeo as per requested by conference committee. That's why Seoul team is so sensitive to funding and financial issues.
> Conference_dev mailing list
> Conference_dev at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Conference_dev