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

Open to new collaborators #42

Open
PabloSzx opened this issue Aug 10, 2021 · 8 comments
Open

Open to new collaborators #42

PabloSzx opened this issue Aug 10, 2021 · 8 comments

Comments

@PabloSzx
Copy link
Member

If you want to collaborate in the project you are more than welcome, feel free to join the Discord https://discord.com/invite/U967mp5qbQ and tell us what you are interested in doing and we will help you to be able to help on it 🎉 👍

@PabloSzx PabloSzx changed the title Open to new contributos Open to new contributors Aug 10, 2021
@PabloSzx PabloSzx changed the title Open to new contributors Open to new collaborators Aug 10, 2021
@trevordilley
Copy link

Would it be helpful to start copying the old issues from gqless into this repo? Perhaps a chance to reevaluate the state and mark which issues are good first issues?

@PabloSzx
Copy link
Member Author

My idea was to simply start fixing them in the gqty repo and then simply notifying that the fix was released in gqty instead of gqless, there are some issues that were already fixed and did exactly that, if you feel like some issues should be copied before, no problem 👍

@nemonemi
Copy link

nemonemi commented Aug 30, 2021

I think there shouldn't be two repositories and names for the same library. Makes things complicated to track.

@PabloSzx
Copy link
Member Author

It's something out of our control, we don't have ownership rights over the gqless org / repo, which is why this "fork" was made

@nemonemi
Copy link

nemonemi commented Sep 1, 2021

Got it!
Could you please point me to a document/article/issue explaining the reason for this fork, if there is such a thing?

@PabloSzx
Copy link
Member Author

PabloSzx commented Sep 1, 2021

Got it!
Could you please point me to a document/article/issue explaining the reason for this fork, if there is such a thing?

There isn't one, I just made a quick announcement in the old discord

@nemonemi
Copy link

nemonemi commented Sep 1, 2021

It would be nice to have some information as to why there's a split, and why should or shouldn't one switch from GQless to GQTY.

I think it would be great if you could please write an explanation at the top of the readme file so that people would know why the change and how we should proceed.

Thanks!

p.s. sorry for extending this thread in this direction.

@huczk
Copy link

huczk commented Sep 7, 2021

I'm thinking that some kind of roadmap or what's missing can be helpful for new collaborators. If someone wants some feature which can be found on a roadmap - it's easier to start collaboration. I'm big fan of comparison that URQL client has made. Maybe we can decide what of those features are needed or nice to have

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

4 participants