Thuzi / facebook-node-sdk

Modeled from the (Facebook Javascript SDK), now with the facebook-node-sdk you can now easily write the same code and share between your server (nodejs) and the client (Facebook Javascript SDK).
Other
736 stars 250 forks source link

Question - Maintained #92

Open dsalcedo opened 9 years ago

dsalcedo commented 9 years ago

This source is maintained ?

dsalcedo commented 9 years ago

:(

alanjames1987 commented 9 years ago

I would like to know this as well.

alanjames1987 commented 9 years ago

I have contacted the company that owns the repo by phone and several times by e-mail and have gotten no response about the state of the module. I assume at this point that it is unmaintained.

dsalcedo commented 9 years ago

Closed. No Maintained

dantman commented 9 years ago

The author hasn't even published already committed releases to npm.

dantman commented 9 years ago

I think the real question now, is do we have anyone (a few people) who are willing to maintain it – accept pull requests, publish releases, etc?

((That isn't rhetorical or anything, if you are willing and capable, especially if you've contributed to the repo before, please say so.))

If we do then there may be a way to move this module forward.

The steps would be something like this:

  1. Try to contact Thuzi again through the emails through the npm owner ls fb email and the individual emails of people associated with the organization and talk to them about maintainers.
  2. Potentially wait around 4 weeks to see if they respond.
  3. If there are maintainers, create a GitHub organization with the maintainers and fork the repo to it.
    • (Ask GitHub if there's a way to transfer/copy bug reports and pull requests)
  4. Find some way to share ownership and do automatic publishing to a npm package.
  5. Contact support@npmjs.com (through npm's Dispute Resolution process) and ask them to transfer control of the fb package.
  6. After a little setup, publish the previous versions of the package to npm.
  7. See what pull requests we can cleanup and accept. What bugs we can fix. Release a new version.
  8. Profit...

I can help a little. Contact people, get the ball rolling on anything that needs to be setup, and find out how we need to configure things to work collaboratively. But I can't dedicate myself to being the primary maintainer.

dantman commented 8 years ago

I've been added as a contributor on the npm fb package and will be moving maintenance of this module to node-facebook/facebook-node-sdk.