"Donation" button for Open Source authors/maintainers #226

Just an idea: we should consider offering some integration to enable a "donate" button for individual git repositories. One solution for European/SEPA countries would be to integrate a QR code for SEPA bank transfers (no fees) to the repo author.

For example, the author of the "Simple Mobile Tools" (Android) has a donation page and prefers bank transfer: https://www.simplemobiletools.com/donate/

Great idea! How well is SEPA via QR supported? https://de.wikipedia.org/wiki/EPC-QR-Code

We could also ask upstream at gitea (if not already possible) to add a donate button which either redirects to the preferred service (like liberapay, patreon, opencollective, paypal, whatever) or shows a dropdown if different ones are available.

I think It would be enouth if the Biography/Description supports markdown

https://github.com/go-gitea/gitea/pull/12415

I think the patch can be applyed to v1.12 branch easely - so codeberg can use this enhancement as patch and dont have to wait for v1.13 to come out :)

@hjacobs and for a git project: just use README.md ?

example: https://codeberg.org/gitnex/GitNex/src/branch/master/README.md

I think https://github.com/go-gitea/gitea/issues/12416 will impruve this eaven more :)

I think the patch can be applyed to v1.12 branch easely - so codeberg can use this enhancement as patch and dont have to wait for v1.13 to come out :)

We usually cherry-pick changes from merged PRs but not unmerged PRs, to keep conflict potential within reasonable bounds.

@hw sure, I wouldn't recommend it either. just keep this as proposal for now :)

@6543: thanks, I did not know that GitNex is on codeberg already 😄

@hw github.com/go-gitea/gitea@2872a04f27

When going with this approach, we should think about additional Markdown sanitizing and/or styling, for example for when someone puts a h1 heading into their profile description, possibly breaking the visual layout of the site.

Also, we'll have to remember to think of this point of Markdown rendering when implementing #196

also disabling external links or camo proxy needed, as embedded images etc would otherwise enable tracking?

For enabling a donation button, enabling external links and images would be essential.

For embedding images, a proxy like in #196 would be needed. Why would we need a proxy for mere external links though? Is it because of the referrer URL?

also disabling external links or camo proxy needed, as embedded images etc would otherwise enable tracking?

this is a general problem

When going with this approach, we should think about additional Markdown sanitizing...

there is already a sanitizing in place - throu didn't tested h1

also disabling external links or camo proxy needed, as embedded images etc would otherwise enable tracking?

this is a general problem

Did anybody try camo/go-camo with gitea yet?

Did anybody try camo/go-camo with gitea yet?

I didn't try go-camo yet. Currently, I'm hoping for some comments on the questions in #196 first.

can we close this?

Why should we? Is it implemented?

well you can just use markdown as suggested (so we do support all donation platforms out of the box based on that) ... user description was not markdown back when issue was created