-
-
Notifications
You must be signed in to change notification settings - Fork 937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate rubygems.org and gittip #505
Conversation
#500 is the relevant issue. |
I see the build is still failing here. I'll make sure to address that as well, before I get to considering this done. |
Just rebased this so it'd be merge-free. Do you prefer it squashed, too? Would've written tests, but I'm not quite sure what to test in this case. |
First step seems to be getting the build green? :) |
Right! |
Looks like it might be unrelated to my changes, but whether it is or not, I'm unsure how to troubleshoot. Will keep poking around. |
Looks probably unrelated, but again, I can't really tell, and I'm not familiar with travis. |
Blah. Those both look like pure Travis failures. I'll try to restart the build. |
Thanks. |
Alright, well I'm just going to start finalizing things and running tests locally until we get this resolved, and then move on to the next steps as discussed in #500. |
Tests pass locally, squashed, rebased, and ready to merge (once it meets your and travis' approval, @indirect). |
Travis says this is good! Thanks for writing this. :) I may be wrong, but I don't see the gittip.png image anywhere in the squashed commit — am I just missing it, or does it still need to be added? |
That! I put it on the other PR, I think, but not this one. Fixing! |
Committed separately (wanted to make sure I got it right, my git is wonky on this clone right now). Squashing presently! |
Alright, this is (at least kinda) alive again! It should be sufficient now for integration to be completed, but there are admittedly at least two deficiencies in the PR as it stands:
On the other hand, @whit537 is ready to wrap up all the gratipay/gratipay.com#233 stuff on this ASAP so the integration can be announced at PYCON this weekend, so I'm willing to really prioritize this as much as I can, if I can just get feedback telling me what's necessary to get this up to snuff quickly. |
Is the plan to announce integration with rubygems, or integration with language package repos at Pycon? |
Just rubygems, AFAIK. No other language community has stepped up to the challenge, so maybe we can shame python into catching up. |
The idea of announcing at PyCon was mostly a joke. :) Though you're right that having this would certainly get the ball rolling on a conversation with the PyPI maintainers. PyCon doesn't need to be a deadline, in other words. Let's knock this out in good form and announce it as we're able. |
That makes more sense. I was too far into analytical mode to notice the joke when I commented, actually. Anyway, I'd love to get this wrapped up soonish. I'm happy to do whatever will help in expediting that. Also, looks like the build failures are unrelated again. 😢 |
@@ -0,0 +1,7 @@ | |||
class Api::V1::ProfilesController < Api::BaseController | |||
respond_to :yaml, :xml, :json, :only => [:show] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty sure that YAML and XML are out as options after the security debacles of late?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm on an old-ish version of the code still, and just followed the convention I found in other controllers as of then. Good catch! Will fix it now.
This looks great to me. I'm trying to get the tests running locally, and then I guess I'll try to kick travis until it gives in and runs the tests again (but I don't think I can do that for pull requests). |
Okay, I just reviewed f39866dbe517c1b71f65c5eeacb3a8927c20cc7f.
|
Bump. |
Happy to merge this once it's ready to go. :) |
Users can add a gittip username to their profile, which will cause their profile page and the gem pages for any gems they own to link to relevant pages on gittip. As well, some API changes were needed so gittip could integrate effectively. These include: 1) gems/:gem_name/owners.:format now includes the gittip_username when the relevant profile has opted in. 2) profiles/:username.:format now exists, and returns profile info.
Alright, I did the link-tweaks requested. The build failure does seem to have been legit last time, but unfortunately I can't replicate it on my machine, even with destroying the databases and rebuilding them before running tests. I've got it rebased onto master, too. |
Integrate rubygems.org and gittip
Closing since this is merged. Glad this finally made it out! |
👯 |
Is this closed or merged? I'm confused. |
Integrate rubygems.org and gittip
Setting up a pull request early and pushing early and often so as to get feedback on any desired changes early. Will update when I actually want this merged.
Also, it's important to note that this is only gem level integration. Maintainer specific integration comes next.
Current status: