-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github Sponsorship button #45
Comments
@mcawley - we're going to have to direct GS on this. We can simply link this to PayPal and set up PayPal to accept notes (e.g. the donor would put TeachOSM in the notes to flag that money towards the project). Or there are many other ways to do this, but we need to start fleshing this out as we have about 6 weeks until the end of July. |
Can we add Ian D to this repo? He is the treasurer and probably best equipped to answer how to most easily set this up. |
Ok we added Ian to the repo. Let's also ask Ian and verify if OSMUS uses Donately or Stripe. |
We have Stripe but in the interest of consolidating all donation information to one spot let's point people to this existing form we have: https://osmus.wufoo.com/forms/openstreetmap-us-donation-form/ |
Sweet! Thanks Ian. |
I just added a donate button to the footer of the dev site. Check it out. |
@d3netxer my opinion only is that I'd move the donate to the header and offset it to the right to make it easier to find. Other than that, looks good! could we remove the 'needs more info' tag now? |
@d3netxer - Donate button looks good up at top - thanks! Seems a bit thicker green atop the text than below right now for me, that's all though, nice & prominent. |
@shawnmgoulet can you try clearing your cache and checking again to see if it updated? Thanks |
Is the donate button a good enough implementation on the site? Or do we want to pursue adding a Github Sponsorship button on the OSMUS Github repo as well? @geomantic |
This is a placeholder for now. TeachOSM has to coordinate first with OSM US on how to best implement.
The text was updated successfully, but these errors were encountered: