-
-
Notifications
You must be signed in to change notification settings - Fork 88
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 call for core contributors/maintainers #116
Comments
I am so far a happy user of Granian and wouldn't mind stepping in and contribute a bit. I already rely on Hyper for some other projects as well, and have a deep interest in networking so should be good. I am not a person with a lot of bandwidth but I should be able to help out as a regular contributor. Feel free to reach out to me for a private chat so we can see how to get started. |
Im down to contribute into the python part :) please contact me via email [email protected] |
Happy to be a maintainer in case of lack of responses arise. |
@GlenDC @achaayb @Andrew-Chen-Wang just to give you all a quick update: I'm currently in the process of moving to a different country, thus I gonna postpone discussion on this to the next month to have proper time and mental room to handle this properly and contact you all privately. Thank you for proposing yourselves for this, talk to you soon! |
I would be happy to contribute and be a maintainer if possible, please feel free to reach me through |
Hello! I have some thoughts about multiprocessing, IPC, and such. If you are still looking for maintainers, I can help with that. I have also started to work on a framework that uses RSGI - while developing it, some ideas also popped into my head :D https://github.com/distantmagic/intention . I intend to base a lot of my open-source stuff on Granian. If you want to talk, let me know. :) |
Hi all 👋
This is an open call for people willing to contribute to Granian in a more structured way.
Granian started as an experiment made on my laptop more than one year ago. At time of writing, Granian gets downloaded several thousands of times, and serves several projects in production environments. These facts and the common sense suggest it might be a proper time to reinforce the project maintainability and credibility, sharing the responsibility and design decisions across more than one person.
Being a core contributor or maintainer would mean to:
Even if current version(s) of Granian are quite feature complete for an HTTP server, a few big themes can already tell the future path for the project like:
I would be glad to discuss the upper points with more people other than me :)
In case you're interested just propose yourself in a comment below, and we can have private chat :)
Also, if you have feedbacks or want to help the project in other ways, you're more than welcome in writing in this issue or contact me directly.
Cheers
The text was updated successfully, but these errors were encountered: