Discord server and better communication

[beepsoft]

Hi all,

I would like to suggest the maintainers of mst-gql to setup a Discord server (or Slack or whatever) to accelerate communication of issues regarding mst-gql.

I'm grateful for all developments going into mst-gql and I understand that it is no one's full time job to develop mst-gql, but a better and more frequent communication about the project may help keeping it (more) alive.

I guess @jesse-savary is still the main maintainer and I've seen @Benz19 acting as "community manager", which is nice, but there's little to no communication about the directions of the project, short or long term roadmap, etc. and the issues and PR-s get answered very infrequently, which makes the project look dead.

I use mst-gql a lot - although not day-by-day - and always need to keep a separate fork to fix issues, which may get fixed in the main version in months or years. This makes developing with mst-gql a bit frustrating.

An open chat channel could make things more transparent and accessible for everyone, and we could discuss and resolve issues more quickly, as well as help new users of mst-gql get started.

Thanks!

[Benz19]

@beepsoft I think thats a great idea - We are all very busy right now and my intent is to help get things back on track. Be patient with me.
I'll chat with @jesse-savary and set something up

[beepsoft]

Thanks @Benz19!

[velidan]

Agree with that. Basically, I'm very interested and excited about the mst-gql as I'm starting a big project based on graphql and I'm looking for a solid solution for that. Previously used apollo for 2 years and now I wouldn't like to come back.
The killer feature is the model's scaffolding and the easy optimistic response and 2 in one. Graphql and Local state. Right now I'm thinking about at mst and urql. However, I don't like such a decision as needing to think about how to sync them between each other etc. mst-gql looks cool and could solve this problem but I'm wondering about the long-term support etc. And I think not only me because the project is just amazing!

[beepsoft]

I think mst-gql could be a viable alternative to Apollo client. Especially if we could implement #4 (I have some ideas for that). But we need better overall communication, roadmap, etc. to show that the project is alive and well.

[ryskin]

Also good to add a discussion tab in github

[beepsoft]

Any progress in this?

[KashubaK]

I've recently discovered MobX and am loving it a ton. I really want my team to adopt it but GraphQL raised a lot of questions that mst-gql elegantly provides great answers for. I think it's a net positive over our current stack, Apollo w/ Redux for local state, but I'd have a much better time convincing my colleagues (and myself, frankly) that using this won't be a mistake if there were concrete maintenance plans.

We're probably going to end up adding fixes and improvements to our own fork as well, given that's a better alternative than not using it at all. If that does end up being the case, I'll certainly do my diligence by adding issues and PRs here when applicable as long as it aligns with the project's goals.

[beepsoft]

Just pinging @Benz19, @jesse-savary. It's been 7 months since the last release. Is there any problem we can help with?

[fullofcaffeine]

Just pinging @Benz19, @jesse-savary. It's been 7 months since the last release. Is there any problem we can help with?

+1

[beepsoft]

Another ping @Benz19 , @jesse-savary. Do you plan to work on the project or is it dead in its current form? What can we do to resurrect it?

[Benz19]

@beepsoft thanks for the ping. - Yes - the plan is to keep working on the project. I'll connect with @jesse-savary today and have him contact you

[jesse-savary]

Hey everyone,

Apologies for the delay in getting back to you all; things have been quite hectic over here. Work has kept me busy, and I managed to get a concussion a few weeks back when I had planned to tackle all this. I'm back now, and we're ready to push the project forward.

I want to assure you all that the mst-gql project is alive, and we're committed to its success. To get things back on track, I've created the following three discussions:

• Announcement: Looking for Trusted Reviewers
• Request for Comment: Towards mst-gql v1.0.0
• Request for Comment: Supporting Legacy (0.x.x) Versions

Additionally, I've set up the Discord server. Here's the invite link: discord.gg/mst-gql. Please feel free to join and connect for real-time conversations, support, and collaboration.

Thank you all again for your patience. We're excited to work together to make mst-gql even better. I'll continue to be available on Discord or GitHub and will do my best to improve response times. If you need help with something and don't want to wait, ping @Benz19 -- he's almost guaranteed to reply within a few hours.