Graphql-flutter: Continuing development of this Project

[juicycleff]

Current State of this Project
So if you are aware of what is happening right now, this repo is not maintained much anymore. I have tried reaching @HofmannZ here but got no reply, hope he reaches back soon. I am however continuing development of this project in my repo which I will share here later today. If @HofmannZ comes back to maintaining the repo, I will, of course, be happy to merge it back into this repo. Thank you.

Here is the new repo https://github.com/juicycleff/flutter-graphql

[olup]

Cool ! So I'll create my PR's on your repo directly.

[juicycleff]

@olup yes sir. I cleaned up and here is the link https://github.com/juicycleff/flutter-graphql

[juicycleff]

I also published to pub dart
https://pub.dartlang.org/packages/flutter_graphql

[juicycleff]

Will be removing the entire branches saving master. I will draw some plans and go from there. But you can send your PRs

[HofmannZ]

Hello everyone,

As you all know we've not been able to maintain this project. This was due to some rearrangements of our resources in private projects. Simply put, we did not have enough time to also maintain this project. As a result, both the issue and PRs are piling up.

We really believe in Flutter, especially in combination with GraphQL and are therefore currently working on a way to keep this project rolling.

We're planning to have a short planning session (SCRUM-ish) this weekend, followed by a coding session this same weekend. Since we look at this as a community project, we'd like to collect as much input as possible. Therefore we're creating a survey to get some general insight into the community. We also like you to join us this weekend with either writing some code or doing some code reviews.

We are excited to pick up this project again, and we hope that you are excited too.

Zino

EDIT: updated the comment with the link to the survey

[juicycleff]

@HofmannZ Nice for you to show back. I will halt whatever I am doing until this weekend. Can't wait to see the outcome 😄

[HofmannZ]

@juicycleff not sure if you get an update when I edit a comment so here’s the link to the survey: https://goo.gl/forms/WZ5JlNWASxd1ojfG3

[wwwdata]

Hi, great that you want to make a survey. But I guess you have to check the permissions. I get an error that says only users in the owners organization can see the form.

[olup]

Yeah, please check settings and open up the form for every one.

[HofmannZ]

@wwwdata @olup Oh, did not know it locks it down by default. Updated the settings, and it should work now!

[wwwdata]

I could not make it past page 2 in the survey.. Clicking the next button does not do anything for me. Was using Chrome browser. I don't know if that is a problem that you can fix or some google forms problem 🤷‍♂️

[HofmannZ]

@wwwdata Could reproduce, looks like it's solved now.

[robert-stevens]

@HofmannZ @juicycleff

This is good news. I think most of us would like to know what is left to get a stable/beta 1.0.0 version and how long that would take between those involved.

If we could have an indication of that by after this weekend it will be great, as that will definitely help other devs in deciding to use this package or not.

[juicycleff]

Hi @HofmannZ, I didn't get a notification. I filled in the survey. What next?

[juicycleff]

@robert-stevens from my test, time should be spent on the cache and also pluggable persistent storage. Following the apollo-link-state pattern, so it is extensible. I am waiting for @HofmannZ plans. I halted my project for this so, I might jump back to dev if it delays too long

[HofmannZ]

Hello everyone,

Thanks for all the great feedback on the survey! We think the answers added some great insights into the project. And since it did not include any sensitive data, we've enabled you to view the results.

We really want to push this project to a stable version and are therefore dedicating more time to maintaining it. We also think it's good to let you guys decide which features will end up in the client. Therefore we're requiring 3 peer-review per pull request, encouraging you more developers to get involved into the pull requests.

Today we also made some first steps by releasing our first beta. You can get it in your project today by requiring graphql_flutter: ^1.0.0-beta.

We hope we can continue building something great!

Zino

[sjmcdowall]

@HofmannZ -- With over 15 years experience with Opensource Software, may I make a humble suggestion and to OPEN this project, since it's so critical to many people, as a real open source with more contributors, people who can pub etc. I would certainly nominate @juicycleff to be a core contributor etc. and maybe 1 or 2 others . That way there isn't a "single" source (1 company) change of being abandoned with no ability for anyone to take over and keep it moving.

[HofmannZ]

@sjmcdowall Definitely a great suggestion! @juicycleff are you open to joining as a core contributor?

[dbanck]

Happy to hear that you guys are back and the development of this great library continues! We've been using the next branch with good success in an internal project so far. ❤️

I like @juicycleff suggestion of following the apollo-link pattern, but I think this somewhat implies a more modular approach to GraphQL in Dart. What do you think of decoupling the internal GraphQL part from Flutter? There are no real dependencies on Flutter when using GraphQL with Dart. Furthermore there could be a smaller library on top of that providing the Flutter widgets (think react-apollo).

This would allow anyone wanting to work with GraphQL and Dart to use the "base" library which is then accompanied by Flutter widgets library for anyone who is using Flutter. Furthermore we could test all the core business logic without having to depend on Flutter.

What do you think? This isn't something which should be done for the release of a stable 1.0.0 version, but might be an interesting thought for the future.

[HofmannZ]

@dbanck When we build the first version of the client, we took a load of inspiration from Apollo. This was done assuming that most people would already be familiar with the Apollo project and could, therefore, find there way around more easily.

The survey showed that the assumption was quite accurate, 89% of the respondents used Apollo before using this client. We, therefore, think it's a good decision to also use the modular link approach. We already made the first link available AuthLink, which does by popular request, provide a single point to provide Authorization.

Decoupling Dart from Flutter is definitely something we would like to do in the future. Though we think the current focus should lay on setting up a solid open source community. Hence we created a poll where we everyone can vote on who should become the new core contributors for this project.

https://goo.gl/forms/19KNF9IMuBKGngrz2

Zino

[dbanck]

There is a lot to learn from Apollo and basing this library on their architecture is definitely a good decision.

@HofmannZ You might have to check the permissions of the new survey, I'm getting the "This form can only be viewed by users in the owner's organization." error.

[HofmannZ]

@dbanck Should be fixed now

[robert-stevens]

@HofmannZ

Thanks for the updates, I am going to check out the beta, any news/progress on optimistic results?

[juicycleff]

@sjmcdowall Definitely a great suggestion! @juicycleff are you open to joining as a core contributor?

Yes, I am definitely

[sjmcdowall]

FWIW -- I'd be ok as a backup publisher / merger / reviewer etc. too if desired...

On Feb 19, 2019, at 11:50 AM, Rex Raphael [e-mail] wrote:

@sjmcdowall https://github.com/sjmcdowall Definitely a great suggestion! @juicycleff https://github.com/juicycleff are you open to joining as a core contributor?

Yes, I am definitely

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/zino-app/graphql-flutter/issues/168#issuecomment-465215354, or mute the thread https://github.com/notifications/unsubscribe-auth/AB8M7Zq4TVhzrTJWvsr5MC4cz05Ucx4Yks5vPCtVgaJpZM4a0PRI.

[HofmannZ]

Okay, the poll has three clear preferences: @cal-pratt, @camuthig and @juicycleff.

Are you guys cool with helping maintain the project? If so, shoot me an email to [email protected] and I'll add you to the project.

[cal-pratt]

@HofmannZ Hey, everyone. Thanks a lot for including me in this vote, but I'm going to take my hat out of the ring. I've become fairly busy with other priorities and havent been able to continue my Flutter experiments as I'd like. I would be happy to help in code reviews or general discussion from time to time, but I dont think I have enough cycles in the day to act as a useful core contributor. Thanks again!

[camuthig]

I appreciate the vote of confidence, but I don't believe I can help out. I haven't worked with Dart since nearly my last commit to this project and already have other projects in the works that are taking up my bandwidth.

[HofmannZ]

@cal-pratt @camuthig I understand that you do not have time to help to maintain the project. I just dropped in all the contributors into the hat ;)

@degroote22 @micimize You both received a load of votes as well. Do you guys have the time and willingness to help to maintain the project with us?

If so, shoot me an email to [email protected] and I'll add you to the project.

[micimize]

@HofmannZ I'd be happy to! I have been fairly swamped recently, but that should be letting up soon and then I'll have time to focus on flutter stuff a lot more.

@robert-stevens (also maybe @juicycleff) It's not robust/tested enough to PR yet, but the most recent work I did on my fork was on adding optimism

[juicycleff]

@micimize that's awesome. Would you like to finish it off, or someone else picks it up?

[micimize]

@juicycleff if someone else wants to pick it up that's fine with me, not sure what condition it's in though - might be out of sync, definitely doesn't have enough tests. I'll hopefully have time to get back to it sometime soon

[juicycleff]

@micimize that's fine. I would like to take a look, but I want to focus on persistent caching for now. However @HofmannZ I didn't get the invitation, did you send it?

[HofmannZ]

Hi @juicycleff, the invitation should've been in your inbox on the 26th. I just resend you the invitation link. Can you let me know if you've received it this time?

[juicycleff]

Yeah I did

[juicycleff]

Thank you :)

[leoafarias]

@juicycleff @HofmannZ There is a lot of discussions internally in our company on which package, and version to use. I assume that after this last few messages, we should stick on using this version of the package which @juicycleff will be merging his improvements and making core contributions to does that sound right?

[micimize]

@leoafarias Yes, unless you want to make use of @juicycleff's changes right this second, that's correct.

[juicycleff]

Correct

[leoafarias]

@juicycleff @HofmannZ sorry, there seems to be now another version of flutter-graphql.
https://github.com/snowballdigital/flutter-graphql

An updated readme on this repository pointing to this new version would be great

[jcraven-worksight]

@leoafarias that is @juicycleff's fork of this repository, although I'm not sure if it's intended to replace this one.

[ChristBKK]

quite confused right now. Which of the repos are maintained now? This? https://github.com/juicycleff/flutter-graphql or https://github.com/snowballdigital/flutter-graphql this? OR https://github.com/zino-app/graphql-flutter ?

[eusdima]

@ChristBKK those two are just unofficial forks and not intended to replace the current one.

[ChristBKK]

@eusdima yeah but this one seems to be lost? isn't @juicycleff maintaining it well? Why can't he takeover or commit to this one here then?

[eusdima]

@ChristBKK The plan was to pick people that are willing to continue developing this repo and @juicycleff was one of them. Since I didn't see him having any activity here, but he maintains mostly his forks, I removed him from graphql-fluter.

[eusdima]

If you want to help the project you can respond to #196

[micimize]

The snowballdigital fork is also @juicycleff's fork. He'll probably consolidate them soon, and has expressed interest in making PR's and consolidating efforts, but has been quite busy (like all of us).

I'd recommend following #197 for tracking the progress we make on consolidation.

[juicycleff]

Hi sorry for all the confusion. My fork at https://github.com/juicycleff/flutter-graphql was little messed up because I had stripped of a lot of this repo branches and tags and did a lot of change to simplify the process of contributing and that was before Hoffman responded. However, I found out the pace of reviewing PRs here was quite slow and is affecting my project and I also have people in my company interested in Flutter and I decided to move it to our organization repo to allow other developers in a haste to get things stable to contribute here https://github.com/snowballdigital/flutter-graphql. As moving forward. The two forks are still quite different from this repo and I am still considering an approach merging in the future. I recently relocated to Norway so I was quite unavailable. I just need to get my project fully functional hence I need a replica of react-apollo asap for flutter, which means I will hold on to my repo for a bit. There are great possibilities to merge in the future, but for now, I just need this on RAD. You can very much use this repo. I plan on getting GraphQL on Flutter as functional as possible, it doesn't matter if it's this repo or my fork. I just need it up and running as soon as possible. I hope this clears out any confusion.

[eusdima]

@juicycleff I am sorry I overreacted about what I said. But I want this project to move forward faster. The goal of GraphQL-flutter was always to become an apollo-client. Would be great if you could join the discord channel referenced in #196 where I would like to hear more about the great work that you are doing in your library and possibly discuss the roadmap.

[juicycleff]

Its fine @eusdima. Sorry I saw the discussion last night, but I had to sleep as it was a bit late and I'm getting used to weather