HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
protontypes
LibreSelery
Python2020–2022
protontypes / LibreSelery · Archived

LibreSelery

Continuous distribution of funding to your project contributors and dependencies. Integrated into GitHub Actions

DevOps & CloudFinance & Commerce
Explore on GitHubRead Hacker News discussions
4Distinct people
10Mentions
0Explicit recommenders
126GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Continuous distribution of funding to your project contributors and dependencies. Integrated into GitHub Actions

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month10 dated mentions

Observed mentions: 2020-09-02 16:50:39 UTC to 2022-09-14 21:08:39 UTC.

02462020-09-01 00:00:00 UTC to 2020-10-01 00:00:00 UTC (exclusive): 7 mentions; 4 submissions, 3 commentsSep 20202020-10-01 00:00:00 UTC to 2020-11-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-11-01 00:00:00 UTC to 2020-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-12-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2021-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-02-01 00:00:00 UTC to 2021-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-01 00:00:00 UTC to 2021-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-04-01 00:00:00 UTC to 2021-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-05-01 00:00:00 UTC to 2021-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-06-01 00:00:00 UTC to 2021-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-01 00:00:00 UTC to 2021-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-08-01 00:00:00 UTC to 2021-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-01 00:00:00 UTC to 2021-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 20212021-10-01 00:00:00 UTC to 2021-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-01 00:00:00 UTC to 2021-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2022-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-01 00:00:00 UTC to 2022-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 20202020-09-01 00:00:00 UTC2020-10-01 00:00:00 UTC743
Oct 20202020-10-01 00:00:00 UTC2020-11-01 00:00:00 UTC110
Nov 20202020-11-01 00:00:00 UTC2020-12-01 00:00:00 UTC000
Dec 20202020-12-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
Jan 20212021-01-01 00:00:00 UTC2021-02-01 00:00:00 UTC000
Feb 20212021-02-01 00:00:00 UTC2021-03-01 00:00:00 UTC000
Mar 20212021-03-01 00:00:00 UTC2021-04-01 00:00:00 UTC000
Apr 20212021-04-01 00:00:00 UTC2021-05-01 00:00:00 UTC000
May 20212021-05-01 00:00:00 UTC2021-06-01 00:00:00 UTC000
Jun 20212021-06-01 00:00:00 UTC2021-07-01 00:00:00 UTC000
Jul 20212021-07-01 00:00:00 UTC2021-08-01 00:00:00 UTC000
Aug 20212021-08-01 00:00:00 UTC2021-09-01 00:00:00 UTC000
Sep 20212021-09-01 00:00:00 UTC2021-10-01 00:00:00 UTC000
Oct 20212021-10-01 00:00:00 UTC2021-11-01 00:00:00 UTC000
Nov 20212021-11-01 00:00:00 UTC2021-12-01 00:00:00 UTC000
Dec 20212021-12-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
Jan 20222022-01-01 00:00:00 UTC2022-02-01 00:00:00 UTC000
Feb 20222022-02-01 00:00:00 UTC2022-03-01 00:00:00 UTC000
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC000
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC000
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC000
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC000
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC101

What Hacker News says

10 sources
protontypes·Sep 14, 2022
We tried something similar in the past: https://github.com/protontypes/LibreSelery Donation were distributed entirely through the CoinBase api by sending emails to each developer in the Git history. I wonder how you will divide the money among the developers. Giving money just to the project maintainers will not strengthen the community. Unfortunately, this is often exactly the area where support is needed to create sustainable open source in addition to fiscal support.
In Show HN: StackAid – Fund all your open-source dependencies
forgotmypw17·Dec 26, 2020
for the nojs crowd, here is page content: Skip to content GitLab Next Projects Groups Snippets Help Toggle navigation Partner Marketing Partner Marketing Project overview Repository Issues 37 List Boards Labels Service Desk Milestones Iterations Merge Requests 1 Requirements CI / CD Security & Compliance Operations Packages & Registries Analytics Wiki Snippets Members Close sidebar Open sidebar GitLab.com marketing Partner MarketingPartner Marketing Issues #314 Opened 5 days ago by @Ly0n0/3 tasks Continuous Funding for the Gitlab Ecosystem - A Free and Open Alternative to GitHub Sponsors Continuous Funding for the Gitlab Ecosystem - A Free and Open Alternative to GitHub Sponsors What are you requesting: Need joint partner content created and/or review Need an integrated partner demo for an event Partner specific customer case studies and
Read the rest
/or stories What cloud / platform provider, integration partner and/or a channel partner does this request include? Institute of Technology and Innovation Management RWTH Aachen as academic partner Coinbase or Paypal as a payment method. Libraries.io for open source dependency scanning. Octobox and opensustain.tech as first Early Adopters CI/CD Platform providers like Gitlab Additional details: Include specific details for this request and/or documents to help partner marketing evaluate the request Our open source community protontypes created a new concept for the funding of software development. We developed a command-line tool for CI that continuously distributes funding between project contributors and open source dependencies. After our first prototyping phase and evaluation, we have distributed around 3000€ between contributors of our own project and collected further requirements from multiple partners like the Debian project or GNU. By successfully applying the concept to our own development we have shown that a free and open alternative to GitHub Sponsors is possible. As many of our partners need a Gitlab integration we are looking for a partnership to lift the prototype to an open, free and independent alternative to GitHub Sponsors that allows projects to switch to any git platform without losing the funding. We are willing to shift the major development repository to Gitlab as we think this will give the project more opportunities and flexibility in the long term. More information can be found here: A Podcast about LiberSelery: https://podcast.sustainoss.org/63 Source code of LibreSelery: https://github.com/protontypes/LibreSelery CI template for LibreSelery Integration on GitHub: https://github.com/protontypes/seleryaction The initial Blog Post: https://protontypes.eu/blog/2020/09/02/launch-of-protontypes... Potential due date: 31.12.2020 Next Steps: Requester will: Link any related issues to this request Provide as much context to this request as possible Partner Marketing will: Evaluate the request against other priorities Ask for more information, if needed Assign the appropriate scope label and resource Provide next step to the requester Questions refer to handbook Edited 4 hours ago by Tobias Augspurger Drop or upload designs to attach Linked issues 0 Tobias Augspurger @Ly0n marked the task Need joint partner content created and/or review as incomplete 4 hours ago Tobias Augspurger @Ly0n marked the task Need an integrated partner demo for an event as incomplete 4 hours ago Tobias Augspurger @Ly0n marked the task Partner specific customer case studies and/or stories as incomplete 4 hours ago Please register or sign in to reply
In A Free and Open Alternative to GitHub Sponsors
protontypes·Sep 4, 2020
A very good point. Solving the problem that you describe is one of the core challenges of LibreSelery. We combine multiple weights calculated based on different project data. Via the GitHub API we can even create weights based on projects activity like merging, code review, issue creation, etc... By the accumulation of multiple weights, we try to avoid rewarding just one behavior. One of the most important metrics will be how much pull requests X have been solved based on the Y issues. We also have a minimum contribution limit that you can adjust for your project. Generally, all weights can be adjusted for each project. By making all payments transparent, everyone involved can see what the distribution looked like in the past. In principle, every company has metrics for the distribution of funds. Unfortunately, these are often very non-tr
Read the rest
ansparent. In contrast, we try to solve the whole thing by combining different transparent movement quantities. You can find more information about this issue here: https://github.com/protontypes/libreselery/issues/132 https://github.com/protontypes/libreselery/issues/159
In Libreselery: Solving the Donation Distribution Problem in Free Software

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.