Handling Sponsors

[cvvergara]

For the moment its ideas on how to handle sponsors

Adam:

For the oceania conference we gave sponsors the instructions for listing as osgeo sponsors, what level they qualify for and so on - and left it to them to reach out to Mike. That seemed to work, at least for the very busy LOC

Michel:

yes, Oceania was great. Maybe what we might need is a form for Sponsors to fill out and then we validate them so that we move the maintenance of the sponsors to them? Maybe a gitea form that emails the sponsor with 3/2/1 months until sponsorship ends? Then the burden is on us to approve when an sponsor updates their info but all the info submission is on the sponsor

Then conferences just send a link to the form, and information about what level they qualify for, right?

Adam:

F4G SotM Oceania levels were not mapped exactly, eg our silver was OSGeo bronze and so on. Mapping exactly would have made the lowest sponsor level too expensive.

Michel:

first thought I had was that we would:

1. Create a git repo for this
2. create an issue form for the info
3. have an form close method that pushes the info to our word press sponsors page

As i think about this, it might be easier to use Google Forms? to create a git issue? The link to publishing a sponsor from a git issue or google form is something we'd have to think about. Some kind of integration with git would be nice as then our sponsor info is version trracked. Something that is currently lacking

Vicky:

About forms: the wordpress have forms: (giving you links to the staging so you can play around)

Michel: the forms in wordpress would be good, but we would like them to push into to git/gitea so we can track changes/version it. Then the sponsors page would need to read from that. Maybe just have the sponsors pages push to git whenever a change is made but the forms would be linked to the sponsors page. It would involve creating logins for each sponsor to manage their pages but thats probably a good idea anyway