Skip to content
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

Who is upstream #43

Open
fgaudin opened this issue Apr 8, 2010 · 3 comments
Open

Who is upstream #43

fgaudin opened this issue Apr 8, 2010 · 3 comments

Comments

@fgaudin
Copy link

fgaudin commented Apr 8, 2010

Hi all, it's not really an issue, but we face to a situation where we have many forks and a dead upstream (sciyoshi). Maybe I've not understand the whole power of github, but I never know which fork to merge to find the function I want. I'm never sure that I implement something new or lacking.

Is there any solution to this, or shall we define a new fork as upstream and update the doc consequently ?

For information, I've merged Mrbouyou's fork.

@jezdez
Copy link
Contributor

jezdez commented May 8, 2010

Actually, I think it's a real problem and needs to be figured out, especially in the light of the new Graph API and the official SDK at http://github.com/facebook/python-sdk/. Are there any leads wrt the future of pyfacebook?

@robmchardy
Copy link

I'm using mirumee's fork as the current 'most-up-to-date' - seems to have merged most others, and has oauth2. http://github.com/mirumee/pyfacebook

Agree with jezdez that it is a problem - would like to carry on using pyfacebook, but if there's confusion over its future, the official SDK may have to be focus from now on...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants