search

rust-ux / uX

Non standard integer types like `u7`, `u9`, `u10`, `u63`, `i7`, `i9`
Apache License 2.0
119 stars 37 forks source link

The maintainer situation going forwad #56

Closed kjetilkjeka closed 1 year ago

kjetilkjeka commented 1 year ago

I apologize for being a terrible maintainer for this project. I want to create a better situation going forward. But I'm unfortunately not going to be able to be much more hands on.

I have moved uX into an organization and my intention is to invite more maintainers. I would especially ask current and previous code contributors to participate. Please let me know to what degree you are willing to help out. The best situation would be if one of the previous contributors could take lead of the situation and make sure it ends up with a structure that would work going forward.

CC: @chrysn @Kijewski @bbaldino @bluecube

chrysn commented 1 year ago

I can't promise to take a very active role, but I'm happy to join a team that keeps this running, and if it's just for reviewing other maintainers' PRs. (Frankly I have no clue about how this is maintained precisely so far, but I figure we'll be going for 4-eyes principle; at least I wouldn't want to wave through my own PR.)

Kijewski commented 1 year ago

I can't promise to take a very active role, but I'm happy to join a team that keeps this running, and if it's just for reviewing other maintainers' PRs.

I'd wholeheartedly say: same. :)

kjetilkjeka commented 1 year ago

Thanks a lot to both of you!

I've added you two as owners to the organization. I'm also going to add the organization to crates.io to make sure we are able to release new versions (that's been neglected for a bit too long already) but It seems like the new team is registered there yet.

Let's do like chrysn say and not approve our own MRs. Other than that let's just trust our gut feeling and don't be afraid to tag in other to get second opinions.

bbaldino commented 1 year ago

I can do my best for that level of commitment as well!

bbaldino commented 4 months ago

@chrysn @Kijewski : I'm trying to spend some time on uX. @chrysn I notice you've done some releases, but how did you do them? The tags are appearing in crates.io but not here in github--it'd be nice to keep the tags here up to date to match crates.io. Also, this release doesn't seem to be the latest code? I noticed this because I was trying to update a project of mine to the latest but it doesn't contain my PR for some missing TryFroms to u1 (this one)

chrysn commented 4 months ago

I don't think I've done any releases. I agree that tags here would be nice; we could start using cargo release, which even has good defaults (I've started setting [workspace.metadata.release] / sign-tag = true in my projects, we may or may not use that). Whatever the past, having another release would be good, we'd just need to doublecheck that there were no breaking changes (I know of none).

bbaldino commented 4 months ago

Ah, I think I was mistaken! I just looked again and saw that it looks like it was @kjetilkjeka who did the release (at least, based on this post).

I'm not aware of any breaking changes either. But before we do a new release we may need to try and manually tag the repo to match the 2(?) releases that were done already otherwise I think we'll be in a confusing situation where crates.io won't match github. @kjetilkjeka did you do the 0.1.4 and 0.1.5 releases? Do you know the hashes? If so we can manually tag them in the repo and then formalize the release process to make sure we remain in sync moving forward.

kjetilkjeka commented 4 months ago

I'm sorry about this, but it seems like those commits (updating the version number) only exists on local branches on a disk that has since been wiped.

0.1.4 is rooted on c3b70a91aa6e4165dd2cda5833d3fabd48ad54a6 0.1.5 is rooted on a875a4cef54be07987b1529008460bac229a7530

Best of luck with the upcoming release!

bbaldino commented 4 months ago

Thanks @kjetilkjeka. @chrysn best we can do may be to tag those hashes with those version numbers?