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

Open
opened 2 weeks ago by hjacobs · 17 comments
hjacobs commented 2 weeks ago

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.

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.
hjacobs commented 2 weeks ago
Poster

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

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

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

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

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.

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.
6543 commented 1 week ago

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

I think It would be enouth if the **Biography**/**Description** supports markdown
6543 commented 1 week ago
https://github.com/go-gitea/gitea/pull/12415
6543 commented 1 week ago

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 :)

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 :)
6543 commented 1 week ago

@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 :)

@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 :)
hw commented 1 week ago
Owner

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.

> 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.
6543 commented 1 week ago

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

@hw sure, I wouldn't recommend it either. just keep this as proposal for now :)
hjacobs commented 1 week ago
Poster

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

@6543: thanks, I did not know that GitNex is on codeberg already :smile:
6543 commented 1 week ago
@hw https://github.com/go-gitea/gitea/commit/2872a04f2796b369fb388c6f34780bbda2e64710

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

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 https://codeberg.org/Codeberg/Community/issues/196
hw commented 1 week ago
Owner

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

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?

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?
6543 commented 1 week ago

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 > When going with this approach, we should think about additional Markdown sanitizing... there is already a sanitizing in place - throu didn't tested `h1`
hw commented 6 days ago
Owner

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?

> > 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.

> 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.
Sign in to join this conversation.
No Milestone
No Assignees
5 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.