You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal here is to talk about some concerns, compile the recent developments, and to ask a question to @chmln.
I'd love to help contribute to this project a bit. It's a nice way to get more hands-on experience with Rust, and support such an awesome project. It seems, though, that maintainership has moved into a grey area since 2024 started (#290, #297, #238), even though people are still using sd and contributing (#292, #193, #296) to it.
@CosmicHorrorDev has recently stepped down (#290) from maintaining the project, with @nc7s also making it known that they won't be able to maintain either. I don't know your relationship (if any) with the other contributors, but it's worthwhile to mention that @dev-ardi has offered to try maintaining, at least a little.
To be clear, it totally makes sense if there aren't any contributors you feel comfortable passing maintainership to. I think what I personally am looking for is a more concrete answer. So, all of that lead-up to ask 1 of 3 things:
a) Do you think there is anyone else that you'd be willing to grant the ability to maintain sd, or b) Is the project better off being archived to let users know it is not planned to be maintained, or c) Do you think the project is in a good place as of now, and doesn't warrant archiving or new maintainers, for whatever reason that might be?
From a concerned user and developer. I wish all of you the best, and appreciate all the work that's gone into this project.
The text was updated successfully, but these errors were encountered:
Hi guys, more than happy to grant maintainer rights to those interested especially if they have any experience with maintaining Rust crates / codebases. I will reread these threads and reach out to those interested
I'm not sure how much of a fork https://github.com/ms-jpq/sad/ is, but it is maintained and seem to have been inspired by sd. Should users either migrate to that package or will it be possible to at least check that sd builds with relative current dependencies with a lock on new features?
The goal here is to talk about some concerns, compile the recent developments, and to ask a question to @chmln.
I'd love to help contribute to this project a bit. It's a nice way to get more hands-on experience with Rust, and support such an awesome project. It seems, though, that maintainership has moved into a grey area since 2024 started (#290, #297, #238), even though people are still using
sd
and contributing (#292, #193, #296) to it.@CosmicHorrorDev has recently stepped down (#290) from maintaining the project, with @nc7s also making it known that they won't be able to maintain either. I don't know your relationship (if any) with the other contributors, but it's worthwhile to mention that @dev-ardi has offered to try maintaining, at least a little.
To be clear, it totally makes sense if there aren't any contributors you feel comfortable passing maintainership to. I think what I personally am looking for is a more concrete answer. So, all of that lead-up to ask 1 of 3 things:
a)
Do you think there is anyone else that you'd be willing to grant the ability to maintainsd
, orb)
Is the project better off being archived to let users know it is not planned to be maintained, orc)
Do you think the project is in a good place as of now, and doesn't warrant archiving or new maintainers, for whatever reason that might be?From a concerned user and developer. I wish all of you the best, and appreciate all the work that's gone into this project.
The text was updated successfully, but these errors were encountered: