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

Maintainers wanted #1356

Closed
flovilmart opened this issue Oct 24, 2018 · 55 comments
Closed

Maintainers wanted #1356

flovilmart opened this issue Oct 24, 2018 · 55 comments

Comments

@flovilmart
Copy link
Contributor

@flovilmart flovilmart commented Oct 24, 2018

Due to new work commitments I am no longer permitted to publish code to, or participate in, this SDK project. Therefore I am seeking a maintainer to take good care of it and ensure it remains up to date.

Please DM me via Twitter (@flovilmart) or respond on this issue.

@flovilmart flovilmart changed the title MAINTAINER REQUIRED MAINTAINER NEEDED Oct 24, 2018
@mtrezza
Copy link
Member

@mtrezza mtrezza commented Oct 28, 2018

The departure of @flovilmart will be a tremendous loss for this community 🙁 Thank you for your commitment and restless support over the years 👍

Let's keep this community engaged and growing as an open source alternative to all the commercial SDKs out there.

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Oct 31, 2018

I would love to help but I don't think I really have the skill set to be of much help. Although if there is anything simple that needs doing like maintaining documentation that I can do I would be happy to.

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Oct 31, 2018

Any help is appreciated, feel free to jump in on open issues, both in this repo and the docs one.

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Oct 31, 2018

I’ll see what I can do 🙂 thanks for all the work you’ve done!

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Oct 31, 2018

@kennic
Copy link
Contributor

@kennic kennic commented Nov 7, 2018

Count me in. I use Parse a lot, and Parse really needs a maintainer, it's outdate. Hope I can help.

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Nov 7, 2018

Awesome @kennic . Feel free to get started any time. If you’re unsure what it involves, feel free to ask.

@SebC99
Copy link
Contributor

@SebC99 SebC99 commented Nov 25, 2018

Wow I haven't seen this. Thanks a lot @flovilmart for all you've done for Parse community!
I don't have the skills and knowledge to be a maintainer but i would be glad to help as much as I can

@jjmaceda
Copy link

@jjmaceda jjmaceda commented Dec 6, 2018

Hey @flovilmart we use parse as an important part of our ecosystem, so is very important for us the continuity of the project, I will like to know more about how we can start helping, what will be the first steps ??

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Dec 6, 2018

@jjmaceda anything that can help the community is a good first step.

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Dec 6, 2018

Also, perhaps modernizing the SDK, and cleanup the dependencies like Bolts. Thinking of Swift as it is the ‘future’.

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Dec 6, 2018

If someone/a group of people could convert the SDK to Swift that would be awesome - I think it would encourage newer devs to participate as many learn Swift only now (myself included).

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Dec 6, 2018

I started a swift SDK based on value types paradigms hère https://github.com/parse-community/Parse-Swift

@jjmaceda
Copy link

@jjmaceda jjmaceda commented Dec 6, 2018

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Dec 6, 2018

Then there is the possibility to embrace graphql as there is a PR for the server that adds full support for it

@jjmaceda
Copy link

@jjmaceda jjmaceda commented Dec 6, 2018

@natanrolnik natanrolnik pinned this issue Dec 17, 2018
@mrmarcsmith
Copy link

@mrmarcsmith mrmarcsmith commented Dec 20, 2018

Thank you @flovilmart! You will be missed! New maintainers let me know what I can do to help.

@flovilmart
Copy link
Contributor Author

@flovilmart flovilmart commented Jan 5, 2019

I have added @mrmarcsmith @jjmaceda @kennic to the people with write access to the repo. If you need more permissions, feel free to ping me.

@ShawnBaek
Copy link
Contributor

@ShawnBaek ShawnBaek commented Jan 6, 2019

@flovilmart I want to contribute this repo too. Thank you.

@stale
Copy link

@stale stale bot commented Feb 20, 2019

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 Stale label Feb 20, 2019
@stale stale bot closed this Feb 27, 2019
@dplewis dplewis reopened this Feb 27, 2019
@TomWFox

This comment was marked as off-topic.

@drdaz

This comment was marked as off-topic.

@brianyyz

This comment was marked as off-topic.

@TomWFox

This comment was marked as off-topic.

@TomWFox

This comment was marked as off-topic.

@drdaz

This comment was marked as off-topic.

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jul 4, 2019

Discussion continued in #1422.

@rico237
Copy link
Contributor

@rico237 rico237 commented Jul 7, 2019

I would love to contribute/help on parse sdk development on a regular basis 🙂

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jul 7, 2019

@rico237 that's great, we're looking to add some more committers to the iOS team so I'll pass this on to the rest of the core team

@funkenstrahlen
Copy link

@funkenstrahlen funkenstrahlen commented Jul 26, 2019

I do not have time to be part of the core team but I will definitely provide PR to help.

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jul 26, 2019

@funkenstrahlen We would love to have you involved! Please contribute as little or as much as you feel willing/able to and let us know if there is anything we can do to help.

There are plenty of existing issues and a few pull requests so feel free to jump in with a review or some guidance etc.

@noobs2ninjas
Copy link
Member

@noobs2ninjas noobs2ninjas commented Jul 26, 2019

I think I'd like to start helping with this as well.

@Husseinhj
Copy link

@Husseinhj Husseinhj commented Sep 7, 2019

I have time and ready to be core team and I'm glad to keeping Parse alive. I have the experience to develop SDKs for Real-time messaging service, Push Notification and API design.
@flovilmart

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Sep 7, 2019

@Husseinhj Great to hear, feel free to jump in on existing issues and PRs or submit new PRs. We’ll add you to the team as soon as it’s appropriate.

@grantespo
Copy link

@grantespo grantespo commented Sep 21, 2019

I've been using Parse SDK for a few years now. Both for android & iOS. I'd love to be a contributor. I love Parse server & find it more convenient to use than Firebase & other back end frameworks. It's truly the perfect platform for a startup to get things up & running fast.

I'm sure there would be a lot for me to learn but I am willing to be a part of the team for the long term vision :)

@SaluBhayo-zz
Copy link

@SaluBhayo-zz SaluBhayo-zz commented Jan 9, 2020

is there any spot available for becoming a contributor, I want to get into the team as contributor

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jan 9, 2020

@salubhayo Absolutely 😀, we loosely follow a meritocratic model (see our governance info), so feel free to jump in on issues and submit PRs and we’ll get you added to the team once we feel it’s appropriate.

@TomWFox TomWFox changed the title MAINTAINER NEEDED Maintainers wanted Apr 13, 2020
@TomWFox
Copy link
Member

@TomWFox TomWFox commented Apr 13, 2020

As an update on this we do now have @drdaz and @noobs2ninjas who are helping out, doing some much needed maintenance.

However, we still could really do with some more help from those who are able to. Alternatively contributing to our Open Collective does help but with this SDK we particularly need some people who can get stuck in - even if it's only for half an hour a week!

@TomWFox TomWFox removed the Pinned label Jul 3, 2020
@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jul 14, 2020

For those who expressed an interest in helping out with the Swift SDK it's a good time to get involved as the project is starting to become active again.

@Husseinhj
Copy link

@Husseinhj Husseinhj commented Jul 15, 2020

@TomWFox
Are there any plans to start this (timing and tasks)?

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jul 15, 2020

@Husseinhj sorry, I don’t understand your question, can you rephrase it?

@Husseinhj
Copy link

@Husseinhj Husseinhj commented Jul 15, 2020

@TomWFox sorry
Do we have any priority for which task should be working on?

@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jul 15, 2020

Got it, good question, I'm not sure. @cbaker6 maybe you could create a new issue with a list of TODOs - or we could create a project board.

@cbaker6
Copy link
Member

@cbaker6 cbaker6 commented Jul 15, 2020

@TomWFox I think the current project board is a good start. Are you able to move "Support for Keychain / secure storage" to "Done"? The rest of the items still need to be worked on.

I'll work on the TODO list, but for now people @Husseinhj and those interested should look at the discussion on what can be worked on here, read to the end of the thread.

How to use/test the current framework is described link below. You can setup a local parse-server and create objects and users by using the Swift Playground Files

Link to how to use the framework: parse-community/Parse-Swift#12 (comment)

@pranjalsatija
Copy link

@pranjalsatija pranjalsatija commented Jul 16, 2020

Just for clarity for anyone who hasn't read through the entire thread @cbaker6 linked, I'm currently working on:

  • Renaming stuff to bring it in line with modern Swift conventions. I'm also moving some files around so the directory structure is a little cleaner, files are more compact, etc.
  • A simple key-value store to save the current user and installation in the Keychain.

I hope to have a PR up around Friday or Saturday, but feel free to pick up anything else in the meantime!

@cbaker6
Copy link
Member

@cbaker6 cbaker6 commented Jul 26, 2020

Those of you looking to help out on the Swift SDK, I added an initial list of Testcases that can be ported parse-community/Parse-Swift#16

@flovilmart flovilmart closed this Jan 23, 2021
@cbaker6
Copy link
Member

@cbaker6 cbaker6 commented Feb 15, 2021

iOS devs,

Parse-Swift had it’s first release (the day Flo closed this issue) and is currently on version 1.1.4.

If you are interested, the easiest way to give Parse-Swift a test drive is to fork the repo and run the ParseSwift.playground in your simulator. ParseSwift.playground Is meant to be a tutorial showing how to use the Parse features you are familiar with. The ParseSwift SDK is not a port of the Parse-SDK-iOS-OSX SDK and though some of it may feel familiar, it is not backwards compatible and is designed with a new philosophy (see more here).

To learn how to setup your local machine and server to work with PareSwift, see here. Also check the API documentation.

What you get with ParseSwift:

  • Modern Swift SDK with zero dependencies. This SDK only depends on the OS
  • Works with iOS 12+, macOS 10.13+, watchOS 5+, tvOS 12+, and Linux (Swift 5.3+). More about ParseSwift compatibility here
  • Supports Swift Package Manager
  • LiveQuery is part of Parse-Swift, requires iOS 13+, macOS 10.15+, watchOS 6+, tvOS 12+, currently not supported on Linux
  • Publishers for all methods, including LiveQuery Subscriptions work with SwiftUI
  • All of the latest querying/fetching features the Parse-Server has to offer (on-par with the JS SDK). See here for all.
  • Supports certificate pinning for parse server and live query server connections, delegates decisions to developer
  • Anonymous, Apple, and LDAP Signin/Authorization, more here
  • Idempotency enabled by default (needs to be enabled server-side to use)
  • PFFacebookUtils and PFTwitterUtils equivalents are ParseFacebook and ParseTwitter. There are also ParseApple and ParseLDAP. Adding support for authentication methods is straight-forward and I encourage you to make a contribution by following this thread.
  • Much more...

Parse-Swift is almost at feature parity with Parse-SDK-iOS-OSX. Some features currently not available:

  • No direct support for local storage. ParseUser.current, ParseInstallation.current, ParseConfig.current, and default ACL, are persisted in the Keychain automatically. If devs want to store other objects, they have to manage this storage on their own. This means no saveEventually, etc. If you don’t need local storage or are already managing a custom local storage, this should be no problem.
  • No ParseUI

You can see the status on future features here.

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

Successfully merging a pull request may close this issue.

None yet