Going your own way with this repo can't be good for the whole Parse community.

Maybe, the Swift SDK was originally under Flo's direction and then under my direction thereafter. I'll continue the SDK on the course that has been set from its origins. It's open-source, so the community can choose which repo better suites their needs going forward. Everyone is also free to contribute to this repo so we can make continued improvements together.

As for the parse community repo, of course devs are can use it if that makes them feel more comfortable. Individuals from the Parse PMC have been attempting to control its direction since the Swift SDK picked up steam, though none of them (or anyone currently part of the Parse governance) contributed to it's design, development, or direction in the first place. Attempting to force direction and design, without understanding the current system is always a bad sign IMO. I suspect, under the Parse PMC's guidance, that particular repo will end up in a similar state as many of the other client SDK's (iOS, Android, Flutter) and be riddled with issues and pending PR's for simple bug fixes that take forever to get addressed.

Also, appreciate you giving a heads up.

Thanks for all the work you have done.

I appreciate you!

I do think it would be of great communal benefit if you do keep it open source, like other examples of your work, but I do think you should ultimately have the choice.

I'm an academic and the reason why I took on Parse-Swift is to create a SDK that can quickly assist with making new research based apps and systems. I collaborate with academia and industry to build these systems so the all of the projects linked in this repo will remain open-source as they should be able to help anyone who needs them.

I'm a researcher, raised by an academic. Share your mission.

Thank you! There's definitely a few things that still need to be working on:

• Adding support for multiple users: https://github.com/parse-community/Parse-Swift/projects/2#card-68137924
• Converting the current ParseLiveQuery to be protocol based. This will allow developers to use other web socket frameworks to conform to the protocol and use LiveQuery on Linux, Android, and Windows: https://github.com/parse-community/Parse-Swift/projects/2#card-68137924
• Create a local storage protocol for developers to conform to (this may not be needed as all ParseObject's are Codable, allowing developers to use other tools) https://github.com/parse-community/Parse-Swift/projects/2#card-53117524

Of course, if you find any bugs or features missing, feel free to open up an issue or pull request

People posting issues on the other repo is okay. Both repos are public, so I can see any issue there. This repo already has a number of fixes ahead of the other repo, over time the amount of features and bug fixes will increase and so will the popularity. The most we can do is post to let people know about this repo and developers will choose for themselves.

Okay, great!

cc: @tanmayb123 @pchelnikov @francocorreasosa @skpaik @Onwa1kenobi @98thpixel @danieltarazona @cmcoffeedev @yingmu52 @madurangae @filmhomage @lmick002 @proactive-solutions @mrtavat @nathantannar4 @zakiso @CJ99 @MobileVet @scinfu @JulienKode @Sadmansamee @mooshee @matheusfrozzi @felnit @Chihpin @FridaySG @johncodeos @DevBakura @churchmediasolutions @pungme @oallouch @otymartin @latne1ec @AbcTM @jaysonng @LilMoke @AMSH92 @kenanbylan @Jack-Adam-Mwanzo @richardtop @DaedalusofCrete @Metadr0n @KamandaK9

👍 @cbaker6, I would recommend that you put a short brief and prominent banner on the very top of the main page of this repo. Just describe what this repo differentiates from the parse-community version including your message from above (I'm a researcher, raised by an academic.) add add some links with background info!

I looked through the discussion thread and I don't see the reason your commits are not being merged. Commits are sitting there from others, as well. What about your development direction differs from theirs?

I looked through the discussion thread and I don't see the reason your commits are not being merged.

@theInternauts It’s not that my commits are not being merged, I’m simply not committing to the parse-community Parse-Swift repo anymore.

Commits are sitting there from others, as well.

The Parse-Swift repo on parse-community currently has no pending PR’s. The Parse-Community repo does have a number of issues, the issues listed as bugs are all fixed in the netreconlab repo latest release. Maybe you are referring to the Objective-C SDK which differs from the Swift SDK? If so, this thread is not about that SDK.

What about your development direction differs from theirs?

My direction is discussed here and is based on the original direction set by Flo and myself. The Parse PMC is locked-in on simply forcing the SDK to operate like the other client SDK’s (Objective-C, JS, Android, Flutter, etc.). Though those are powerful, they are based on the archaic design architecture created when Parse was owned by Facebook and pre-dates when the ecosystem was open-sourced (for example, Swift 1 wasn’t released when the original Parse iOS SDK was released, we are now on Swift 5.7). They will eventually force in dependencies, make the code clunky, and restrict the capabilities of Parse-Swift either on-purpose or through lack of understanding of the current design of the Swift SDK. The direction I’ve carried Parse-Swift in has led to the most flexible Parse Client SDK to date, the most feature rich SDK, the only SDK with zero dependencies, 1 of 2 SDK’s that works with Cloud Code (the other is the JS SDK), all of which works on all Apple platforms, Linux, Android, and Windows

Just wanted to drop in and say I too appreciate all your hard work on Parse-Swift for the community. Thank you very much!

Thanks @dblythy! I’ve enjoyed your improvements, bug findings, and discussions as well!… Also, wonderful work you’ve been doing on the server, your additions are valuable improvements.

I do believe the parse-community appreciated my contributions. My gripes are more with 1 PMC member and how blanket authority is asserted without accountability, knowledge, and lack of checks and balances for this member. In addition, this person attempts to act as if they are someone’s “boss”. For example, one time they direct messaged me after a blog came out about Parse-Swift telling me I need to contact and verify with them about what I plan to say in future blogs/interviews as if I needed approval from them. These types of requests are absurd and are a sign of a “power trip”. The PMC consists of many people, yet only the one speaks on behalf of all of them in the last year or so. I enjoyed the PMC when they had Tom and the others interacted with the community and on repos.

@cbaker6 I just read through the 5.0.0 changelog. You have done a very good job. Keep it up!

Thank you for the information! Was not aware. I used the docs from back4app and unfortunately they do point to this old community version.

Thanks again for cc'ing!

For those interested in latest releases of ParseSwift, please see the threads above/

cc: @Chtapodi0 @GoStraight-Tech @antjumper @cspell2k5