{"action":"created","issue":{"url":"https://api.github.com/repos/gratipay/inside.gratipay.com/issues/441","labels_url":"https://api.github.com/repos/gratipay/inside.gratipay.com/issues/441/labels{/name}","comments_url":"https://api.github.com/repos/gratipay/inside.gratipay.com/issues/441/comments","events_url":"https://api.github.com/repos/gratipay/inside.gratipay.com/issues/441/events","html_url":"https://github.com/gratipay/inside.gratipay.com/issues/441","id":122655450,"number":441,"title":"partner with Chocolatey","user":{"login":"whit537","id":134455,"avatar_url":"https://avatars.githubusercontent.com/u/134455?v=3","gravatar_id":"","url":"https://api.github.com/users/whit537","html_url":"https://github.com/whit537","followers_url":"https://api.github.com/users/whit537/followers","following_url":"https://api.github.com/users/whit537/following{/other_user}","gists_url":"https://api.github.com/users/whit537/gists{/gist_id}","starred_url":"https://api.github.com/users/whit537/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whit537/subscriptions","organizations_url":"https://api.github.com/users/whit537/orgs","repos_url":"https://api.github.com/users/whit537/repos","events_url":"https://api.github.com/users/whit537/events{/privacy}","received_events_url":"https://api.github.com/users/whit537/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-12-17T03:48:02Z","updated_at":"2015-12-19T20:13:22Z","closed_at":null,"body":"From @ferventcoder in private email, shared with permission:\r\n\r\n> My name is Rob Reynolds, I'm the primary maintainer of [Chocolatey](https://chocolatey.org/), a package manager for Windows. We have a community feed where the community creates and maintains packages for all kinds of Windows software. All that sounds great, but it does come with one minor issue - maintainer drift. We have maintainers who come in at certain points and create packages for software they use, but as they move to other platforms and/or stop using those bits of software, they leave behind packages that need new maintainers. Packages can have multiple maintainers so it is usually pretty easy for us to handle that when newer folks come along.\r\n>\r\nI've been thinking about ways to reduce maintainer drift for the last three years and I keep coming back to the idea that users of those packages could come along and provide a one time or weekly tip to incentivize the maintainer(s) to keep the package updated. This and a reputation system I feel will go a long way to reduce maintainer drift.\r\n>\r\nWhat I would like to do is to work with an API that\r\n>\r\n- Doesn't disclose the receiver email addresses when donating (or really ever)\r\n- That allows a user to donate to the maintenance of a package, whether by one user or multiple users does not matter - so they are donating to a group, not an individual\r\n- Because maintainers come and go, that donation group needs the ability to adjust automatically.\r\n- The donation group should automatically split between the package maintainers (even if they have not yet claimed their account - we know their email address ahead of time)\r\n- The donation team would need to be collecting funds before users even signed up that were considered part of the team.  \r\n>\r\nI've seen Gratipay as something that is very close to meeting all of these needs. I know you've made some recent changes that may make this less approachable for Gratipay proper. e.g. I saw that you are now reviewing every new team. I'm proposing 3K+ donation groups immediately (one per package) and automatically adding a donation group as new packages are created.\r\n>\r\nHave you thought about supporting scenarios like this? Would you consider allowing this / creating a similar service to Gratipay that would allow for this? Alternatively, do you know of any service that does something similar to the above? If we can't find anything else, it's likely we would need to build our own and I'm not really wanting to step into that market. \r\n>\r\nI'm not sure whether this would even be an attractive use case for you as we have a smaller community than Github, but we do have a growing community with over 30 million package downloads in four years (25 million in this last year alone). One thing to consider is that we're just one group that would be interested in something like this, I'm sure other FOSS communities would also be interested."},"comment":{"url":"https://api.github.com/repos/gratipay/inside.gratipay.com/issues/comments/166021047","html_url":"https://github.com/gratipay/inside.gratipay.com/issues/441#issuecomment-166021047","issue_url":"https://api.github.com/repos/gratipay/inside.gratipay.com/issues/441","id":166021047,"user":{"login":"webmaven","id":438502,"avatar_url":"https://avatars.githubusercontent.com/u/438502?v=3","gravatar_id":"","url":"https://api.github.com/users/webmaven","html_url":"https://github.com/webmaven","followers_url":"https://api.github.com/users/webmaven/followers","following_url":"https://api.github.com/users/webmaven/following{/other_user}","gists_url":"https://api.github.com/users/webmaven/gists{/gist_id}","starred_url":"https://api.github.com/users/webmaven/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webmaven/subscriptions","organizations_url":"https://api.github.com/users/webmaven/orgs","repos_url":"https://api.github.com/users/webmaven/repos","events_url":"https://api.github.com/users/webmaven/events{/privacy}","received_events_url":"https://api.github.com/users/webmaven/received_events","type":"User","site_admin":false},"created_at":"2015-12-19T20:13:22Z","updated_at":"2015-12-19T20:13:22Z","body":"If we can solve this for Chocolatey, offering similar access to other package repositories for integration ( [npmjs.com](http://npmjs.com), [pypi.python.org](http://pypi.python.org), [rubygems.org](http://rubygems.org), [packages.ubuntu.com](packages.ubuntu.com), etc.) would be a huge force multiplier. :rocket: "}}