-
Notifications
You must be signed in to change notification settings - Fork 13
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
NOT actively developed #54
Comments
I see no such claim. Also not sure why you felt the need to create this issue when you've contributed nothing yourself. |
@jgillich, look at this:
I did not mean to disregard your work which I highly respect. However, when the stats are so low, the maintenance status of the project should be more clearly communicated.
|
The claim is in the comparison table in the README in https://github.com/graphql-crystal/graphql/tree/01eeb92cc4cac2f60e11a0a1ef80f9d23ba7ab1b/ |
So are you offering to step up? I don't owe you anything. Welcome to open source. You were able to figure out that there hasn't been much activity lately, so are others. |
You did not answer my questions. Yes, I figured out there is not much activity, but as I explained in this comment, this can mean multiple situations. Which one applies to this project? |
Do you see open PRs? Contributions are welcome, demands are not. |
See, you treat me like I'm responsible for maintaining this project, like it's my job. It's not. I built this a few years ago and put it on the internet because I thought it would be useful to others. That's it. I never promised to maintain it till the end of times. I certainly don't need to respond to open issues if I don't want to. Development will happen if someone steps up and does the work, but not sooner. You will find that it works this way with most projects. |
I did not meant to treat you like you are responsible for developing this.
That's what I was curious about. Anyway, thanks for your work. |
Please change the README. It states that this library is actively developed, which is not the case.
The text was updated successfully, but these errors were encountered: