Skip to content

Project dead? #1101

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

Closed
boardmain opened this issue Feb 1, 2017 · 18 comments
Closed

Project dead? #1101

boardmain opened this issue Feb 1, 2017 · 18 comments

Comments

@boardmain
Copy link

hi it is a good idea to start a project using this sdk or it need to be considered dead? i see last commit was 7 months ago

@ShawnBaek
Copy link
Contributor

nope. Parse is still alive and works fine

@jeffMeador
Copy link

It's dead. Bad idea.

@brianyyz
Copy link

@jeffMeador are you / were you a user of Parse? I'm interested in why you say that it is dead. What would the good idea be now for the formerly happy parse.com users?

@jeffMeador
Copy link

The parse-server repo looks healthy and active, but the iOS & Android repos have had almost no activity in 7 months. As time goes on they will deteriorate.

@Abderezai
Copy link

Crap, I need to Facebook utils V4 and the latest ios sdk only has bolt and parse. The podfile also does not work for Facebook SDK v4. Any ideas?

@ShawnBaek
Copy link
Contributor

@Abderezai
Copy link

I did and I ended up just copying the ParseFacebookUtils folder in my project and referencing that. Would have preferred a framework drop in. I also went and downloaded the FBSDKCoreKit and FBSDKLoginKit frameworks from facebook's developer website. Does this sound right to you? Still trying to workout all the details, the api is different.

@skparticles
Copy link
Contributor

Guys, Please help us.

#1108
#1109

@jeffMeador
Copy link

There are a few ways out of this

  1. Get ownership of Parse iOS & Android repo transferred to people who will maintain it.
  2. Start a new open source Parse iOS & Android project.
  3. Interact with the Parse REST API directly.
  4. Start migrating to another service.

@brianyyz
Copy link

@hramos @nlutsenko @gfosco Your thoughts / comments on this thread please.

@ShawnBaek
Copy link
Contributor

I hope this repos to be updated.

@hramos
Copy link
Contributor

hramos commented Feb 16, 2017

Hey everyone, we've been busy recently working to make the Parse.com shutdown go as smoothly as possible. Next up we need to discuss how all of these repos will be maintained going forward. We have a healthy and active project at parseplatform/parse-server thanks to a core group of contributors, but we have yet to identify people who can perform code reviews and take ownership of these other related repositories. Until we are ready to announce how exactly we will be doing this, feel free to chime in if you can commit to be an active maintainer for any of these repos.

@ChrisGrant
Copy link

@hramos I'd be interested in being a contributor. Never sure how much time I'm going to have but I'd love to help out whenever possible!

@michael-mansour
Copy link

@hramos any news ?

@danielblx
Copy link

danielblx commented Mar 28, 2017

Parse will never die 👍

Here in our company we publish a productivity library that helps insert, update and query on Parse Server using the Xcode interface builder.

https://github.com/Ilhasoft/ISParseBind

@stale
Copy link

stale bot commented Sep 19, 2018

This issue has been automatically marked as stale because it has not had recent activity. If you believe it should stay open, please let us know! As always, we encourage contributions, check out the Contributing Guide

@stale stale bot added the wontfix label Sep 19, 2018
@hramos
Copy link
Contributor

hramos commented Sep 19, 2018

Parse was formally transferred to community ownership last year, as evidenced by the switch to the parse-community organization this is now hosted under.

I think we can close this as resolved.

@stale stale bot removed the wontfix label Sep 19, 2018
@stale
Copy link

stale bot commented Nov 3, 2018

This issue has been automatically marked as stale because it has not had recent activity. If you believe it should stay open, please let us know! As always, we encourage contributions, check out the Contributing Guide

@stale stale bot added the wontfix label Nov 3, 2018
@dplewis dplewis closed this as completed Nov 4, 2018
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