Gittip Support on Packagist

[clone1018]

Gittip is an open-source platform for sustainable crowd-funding. Gittip lets you set up small weekly anonymous donations to people who do great work. It's particularly well-suited for open source programmers and projects.

Integration would Gittip would be super simple, I'm working on the Gittip Anywhere plugin for Google Chrome which adds support for Gittip on your favorite sites (right now GitHub):

We've added a Gittip link under Maintainer, like:

but of course implementation design is up to you guys (buttons are cool too!).

Anyways, looking forward to hearing back soon!

[Seldaek]

I am a bit reluctant to do this because some people submit packages for others, so the maintainer isn't always accurate. Also from what I have seen in the past with pledgie, paypal buttons and whatnot, such donation things for OSS rarely work well.

[Seldaek]

Don't get me wrong, not entirely against, but maybe reading the email of the author if it's provided would be best? I don't know how gittip works in detail so not sure what is feasible.

[clone1018]

Integration would be simple with Packagist as it would all depend on the "authors" email in the composer.json file, we're currently working with RubyGems to integrate Gittip with their service, and they had (kind of) the same problem, they only have the users email. The solution we've come up with over there is to add some new hooks to our service (Gittip) to better support sites where you have "packages" and "teams", we've already done that with Github (see composer) and we're working on it with RubyGems, you can check out where we are here https://github.com/whit537/www.gittip.com/issues/223#issuecomment-11340649 . If you are interested in it we'd love to work with you, even write Packagist code for the implementation based on how you see fit.

As for the future of Gittip, I can't promise anything that I don't know for sure, but the idea of Gittp (in my opinion) has the power to change how developers are funded, instead of them working 40 hours a week at a "do what you're told" corporation, they can sit at home, developing what they love to help the programming community. I think the simple idea of "doing what you love" without worrying about how you'll pay your electric bills, will really entice people into at least trying Gittip, however, that has to start somewhere, why not here?

[Seldaek]

Another option for authorship: for packages hosted on github (read the Canonical URL), is to use that to identify the orga/user. That's 99% of the packages so it's a pretty good start.

[clone1018]

That could work great too, but what about for packages not on Github?

[Seldaek]

Is it really a big deal not to show it for the <1% that are not on github? Obviously in that case we could fallback to author email or such if available, but at some point I'd rather not show the button than grab the packagist maintainer blindly.

[clone1018]

No, it's not, either is fine by me and in the end up to you guys.

[chadwhitacre]

@Seldaek Thanks for being open to this. :-) My concern with going off the canonical URL is that it means forcing Gittip on users whether they want it or not (right?). Gittip got burned early with an opt-out approach, and I'd be much more comfortable with an opt-in approach where we go off a "gittip_username" (or whatever) key in composer.json.

[mhujer]

Meanwhile, the gittip was renamed to gratipay.

And the link to it was added to RubyGems rubygems/rubygems.org#500 and then it was removed in 2014 rubygems/rubygems.org@7828906 (if favor of Linkset instead of specific service rubygems/rubygems.org#500 (comment))

If "tipping" for developing open-source packages takes off it may be better to have something like "donation" field in composer.json to be platform independent.

So I guess this issue can be closed for now, right?

[Seldaek]

Yup we can probably close until further notice..