-
Notifications
You must be signed in to change notification settings - Fork 2
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
Future of this project #1
Comments
I would be happy to merge your changes and continue maintaining them :) |
Sure! I'll open a PR then |
Btw, I do already have an open PR in nixpkgs for this now, with myself added as a maintainer for this package. I would simply change the |
That's fine as long as they've confirmed agreement. And "maintainer" in nixpkgs mostly means getting pings about issues/PRs; anyone can submit a PR to update the package. |
In that case, it would probably make sense to just do everything in one PR. @AgathaSorceress: If you'd like to, I could add you to the maintainers list of this package in my PR. However, you also don't seem to be in |
I just merged your changes, can also make a release/tag if it would be useful. I think it makes the most sense for you to merge your PR and for me to just add myself as a maintainer later. |
Neat, thanks! A tag is not really necessary I think |
Hey, as you might have seen in the nixpkgs issue regarding this, I have recently forked this repo in order to implement
pkgs.formats.kdl
in nixpkgs. That implemention (https://github.com/feathecutie/nixpkgs/tree/formats-kdl) is basically ready to be upstreamed now, but would also requiring packaging some version of this project in nixpkgs.Are you interested in me contributing my changes back into this repo, in order to make this repo the main codebase that gets packaged? Otherwise (if you're not interested in continuing to maintain this), I would simply upstream my fork of this repo instead.
The text was updated successfully, but these errors were encountered: