is pyfacebook an active project?

[Aljosa Mohorovic]

although i'm aware of activities on github it doesn't seem to me like
pyfacebook is actively developed or used on day to day basis.
i've been using pyfacebook on a live site (and some projects based on
pyfacebook) ~45 days and i'm surprised with things i've noticed in
this period.
there doesn't seem to be activities to track facebook official roadmap
or to resolve current issues.

but mostly i'm surprised that there is no discussion on pyfacebook
group (only some info on github issues) which makes me think that
there are no people actually using pyfacebook.
since i've started i had issues with cookies, iframe situation, webkit
based browsers, cache, expired session and other situations (this is
not a problem, there are always issues with any software and naturally
it takes time) but no discussion on pyfacebook group.
at first, i thought that this is something connected with my code but
looking at facebook developer forums i've found out that there are
users (not using pyfacebook) that have issues mentioned before.

my intention with this post is to figure out what will happen with
pyfacebook in next couple of months and should i spend my time trying
to improve pyfacebook or look for another solution.
i'm currently using pyfacebook on daily basis at work and am in
position that i must support facebook platform so i'll try to
positively contribute to pyfacebook.
how many people are actively using and depend on pyfacebook? are you
willing and have time to get involved?

Aljosa Mohorovic

[Andrés Mejía]

What you say is very true. When I tried Pyfacebook, I reported a couple of bugs on Github's issue tracker but never got a reply. I didn't want to fix them myself, so I moved along and am now using Ruby on Rails with the Facebooker plugin.

In brief: I think Pyfacebook is a dead project.

--
You received this message because you are subscribed to the Google Groups "pyfacebook" group.
To post to this group, send email to pyfac...@googlegroups.com.
To unsubscribe from this group, send email to pyfacebook+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyfacebook?hl=en.

[Miguel Rodriguez]

Hi Aljosa,

We're currently facing a similar situation: we are using pyfacebook for some of our products and were wondering if it was a safe bet.

So, responding to your question: 

yes, I would be very interested in helping maintaining pyfacebook. In fact we already did some small modifications to add dashboard support (since notifications are no longer possible).

Cheers,

Miguel

[Miguel Rodriguez]

It's only dead if we let it die.

I'm in for moving it forward. Anybody else?

2010/3/3 Andrés Mejía <and...@gmail.com>

[Samuel Cormier-Iijima]

Hey everyone,

I haven't had time to put in much work on PyFacebook given that I
stopped actively developing apps a while ago. So the problem is that I
haven't kept up with the latest API additions enough to know what kind
of things need to be done.

There's a lot of forks on GitHub which seem to be more actively
maintained; I'm sure many of those have support for the latest
additions, bug fixes, etc. Every once in a while I get around to
pulling those back into my branch though...

--
Samuel Cormier-Iijima <sciy...@gmail.com>
http://sciyoshi.com/

[David]

I'd be interested in helping pyfacebook (if I was knew more python
>.>) as I just want to be able to post/get status from it, which, due
to the limited support/tutorials, doesn't seem possible in it's
current state. However I don't know how to work with Facebook's API
so I'm kinda worthless...

> Samuel Cormier-Iijima <sciyo...@gmail.com>http://sciyoshi.com/

[Aljosa Mohorovic]

On Mar 3, 9:48 pm, Miguel Rodriguez <miguel.rgonza...@gmail.com>
wrote:

> It's only dead if we let it die.
>
> I'm in for moving it forward. Anybody else?

maybe we should organize issues and contact owners of forks on github
to participate in discussion.
organizing github issues in labels like auth, new features, fb canvas/
iframe, docs and similar so that everybody who wants to help can focus
on a specific thing.

if we could organize just a few people to work on issues or give ideas
how to solve issues it would be a good start.
i'll be focusing on fb canvas/iframe and contacting people with forks
on github.

Aljosa

[Michael Robellard]

Samuel,

You have done a great job with pyfacebook, but since you are not
actively working with facebook apps perhaps the pyfacebook community
should take the app and have someone else be responsible for it. There
are currently 16 forks in github of pyfacebook that have each solved
various bugs with pyfacebook, I and probably many others are using
pyfacebook on a daily basis and it would be great if someone took it
over, merged in all the changes, and continued to merge patches
provided by the community.

I looked and saw that there were two other easily found (facebook
wiki) python facebook libraries (simple facebook and minifb) however
the problem with them and I believe the advantage of pyfacebook is
that they are very small wrappers around the rest call to facebook, so
to use them you would do minifb.call("facebook api function", params)
which isn't very pythonic or in the spirit of the facebook api as
written in PHP. I think that the pyfacebook api takes the right
approach and we should continue to use it.

Any thoughts anyone?

On Mar 3, 5:07 pm, Samuel Cormier-Iijima <sciyo...@gmail.com> wrote:

> Samuel Cormier-Iijima <sciyo...@gmail.com>http://sciyoshi.com/

[jskitz]

Hi Michael,

I also would like to see this project start moving forward as I'm
relying on it for a couple projects that I'm working on at the
moment. I'm also interested in django-facebookconnect, which is also
a project that seems fairly inactive at the moment. It is suffering
from the same problem; there are multiple forks on github, but it's
fairly difficult to know which master is the most current, as there is
not much merging going on. I reached out to Ryan Mark about 3 weeks
ago to see what the status is on django-facebookconnect, and that I'd
be willing to help out on that as well. I have not heard back from
him yet. Probably django-facebookconnect and pyfacebook should be
merged into one project in the future.

I've reached out to Aljosa to say that I'm interested in working on
this project in whatever capacity makes sense. I haven't been working
on it long enough to feel confident in being the maintainer, however I
do have the bandwidth right now to put in some time on this. Last I
heard is that Aljosa is reaching out to people who have forks on
github to try and rally the troops. He can probably provide more
information on where we are at currently.

Let me know how I can help...I'm ready and willing,

-Jason

[Sam]

On Fri, Mar 19, 2010 at 7:40 PM, jskitz <jsk...@gmail.com> wrote:

Probably django-facebookconnect and pyfacebook should be
merged into one project in the future. 

No, django is not python.  It would be very hard to merge the two.  I would prefer having it im pure python than django-ese.

--
Ubuntu FTW!

[Asaf Ravid]

I think django is very useful, I used it to create a very good facebook app

--

You received this message because you are subscribed to the Google Groups "pyfacebook" group.
To post to this group, send email to pyfac...@googlegroups.com.
To unsubscribe from this group, send email to pyfacebook+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyfacebook?hl=en.

--
Asaf - אסף

[Sam]

*OT* django is powerful, but it doesn't use python to its potential

--
Ubuntu FTW!

[jskitz]

Hi Sam,

I agree with you. However, pyfacebook already comes with tools to
work with Django, App Engine, and pure WSGI, so it is these parts that
I was referring to when talking about merging django-facebookconnect
with pyfacebook. From a project perspective, it is confusing to have
to use both pyfacebook (with djangofb) with facebook-connect to get
this rolling with Django 1.x.

-Jason

[Aljosa Mohorovic]

On Mar 20, 3:40 am, jskitz <jsk...@gmail.com> wrote:
> I've reached out to Aljosa to say that I'm interested in working on
> this project in whatever capacity makes sense.  I haven't been working
> on it long enough to feel confident in being the maintainer, however I
> do have the bandwidth right now to put in some time on this.  Last I
> heard is that Aljosa is reaching out to people who have forks on
> github to try and rally the troops.  He can probably provide more
> information on where we are at currently.

i didn't have enough time but i've sent messages via github to couple
of people with recent commits and asked them to join discussion here.
what we actually need is a fork of pyfacebook to track and share bug
fixes, ideas and general help.
i think that anything else is currently not important because without
a master to track everything else fails.

Aljosa Mohorovic

[Miguel Rodriguez]

Agree. 

I have some small corrections/additions that dont know where to merge to, and creating another fork does not look like an option to me....

Aljosa Mohorovic

[woodcoder]

Hi there

Like Miguel, I have only a few small additions - I don't have a lot of
time, but happy to contribute some to help with merging and testing.

Andy...

On Mar 22, 12:57 pm, Miguel Rodriguez <miguel.rgonza...@gmail.com>
wrote:

> > pyfacebook+...@googlegroups.com<pyfacebook%2Bunsubscribe@googlegrou ps.com>

[woodcoder]

Hi there

I'm currently working with pyfacebook too - and, like Miguel, have
some small additions too.

I don't have a lot of time to contribute, but happy to help here and
there.

Andy...

On Mar 22, 12:57 pm, Miguel Rodriguez <miguel.rgonza...@gmail.com>
wrote:

> > pyfacebook+...@googlegroups.com<pyfacebook%2Bunsubscribe@googlegrou ps.com>