Where should future development happen? #350
Replies: 2 comments 1 reply
-
Thanks for making the contribution :)!
Indeed, development there seems to have stalled despite already being somewhat usable. Originally I created that group and was an owner, but have recently removed myself from it due to the inactivity and me not working on it anyway. This might be useful context for…
The only place where I have control is this repository, and despite me wanting to see it being replaced by an alternative implementation, it really seems there's life in the old dog yet. Thus I welcome you to make this project maintainable once again in any way you see fit. It would be great to see the makefile/buildsystem repaired and CI working again, for instance 😅. Eventually, and if you are interested, I will happily welcome you as co-maintainer of these crates in which you seem to have great interest, possibly culminating in ownership transfer if you want. After all, I am not using these crates myself and maybe everyone would be served better if they were in the hands of someone who has greater need for them. In any case, please be welcome to contribute here and take these crates into the future - I think they are valuable for the Rust ecosystem and deserve to be kept in better shape than they are in now. |
Beta Was this translation helpful? Give feedback.
-
I've been making some progress at kylegentle:python_fixes. My intent for this first chunk of work (and likely the next few) is to make incremental refactoring & type annotation changes without modifying the behavior of the codegen. I've verified this by re-generating all APIs at the base and tip of my local branch; the only changes are to the "this file was generated automatically from x" lines, as I've moved & renamed some things. If you like what you see so far, I'm happy to submit a PR, or copy the branch here and continue working. Just let me know what kind of workflow you'd prefer. I'm certainly open to the idea of co-maintaining the crates in the future; let's see where this improvement effort goes! 😄 |
Beta Was this translation helpful? Give feedback.
-
Hey @Byron! Thanks again for your help enabling custom connectors for
hyper
clients in #338.I'm interested in contributing some further work to these crates, specifically:
admin
APIs to generate successfullyI noticed that there's an alternate implementation with some nice design goals, but it seems like most recent activity has been limited to the original implementation, and this repo is still where all the crates are generated & published from.
Personally, having more experience with Python than Rust, I'm probably better equipped to contribute here. I'd be happy to make some incremental refactors aimed at cleaning up the Python + Mako codebase. But I don't want to further diverge the project if it's still planned to move forward with the newer implementation.
Where's the best place to direct my effort?
Beta Was this translation helpful? Give feedback.
All reactions