-
Notifications
You must be signed in to change notification settings - Fork 891
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
Crow is being maintained elsewhere
#387
Comments
@The-EDev How does the linked fork relate to this repo? Should we jump over to your fork, will you migrate your changes in here at some point? |
@The-EDev Which fork do you recommends as the replacement? |
@The-EDev Thanks |
@The-EDev I think it might be a good idea to advertise the new repository so that people won’t treat this project as ‘unmaintained’ and the contribution effort will be centralized. |
I would honestly love to further advertise the new repo. I have already commented wherever I can here, I bought https://crowcpp.org , and I've added crow to a couple of wikis. I would like to also go on some social media like reddit, but I don't want to have accounts there because of the whole data theft issues. Why don't you join our gitter and we can discuss this stuff there. Perhaps we can find people willing to spread the word around or make specific suggestions on how to improve the general PR. |
@The-EDev - Would be great to have a login and authentication example to add value to the project. Then it would be real useful. |
Agreed, I was working on an HTTP Authentication tutorial, but couldn't get it done in time, will hopefully be in the next batch of doc updates :) |
Crow is being maintained elsewhere
This is just to notify anyone interested in Crow that it is being maintained by @mrozigor and myself here.
We've added many features and fixes (even released a new version), we also have travis running, documentation, and even small changes to the logo.
Any help is welcome, feel free to add issues, solve existing ones and send PRs, or with us about the project.
P.S. We have contacted @ipkn about this subject using different methods, and have yet to receive a response.
The text was updated successfully, but these errors were encountered: