Unmaintained?

[karlhorky]

Hi @stkb, first of all, thanks for all your effort working on this project!

I wanted to reach out about this project being potentially unmaintained - it seems like the last commit it received was in March 2022 and there are multiple unreleased Pre-Release versions with great features:

• Release 17.7 Pre-Release as main published version? #391

If you don't think that you'll be available to maintain this longer term, would it be time to ask for a community maintainer to help out?

[dnut]

@stkb has had no activity whatsoever on github since February 2023.

This project is stale with a lot of outstanding issues that the community has shown interest in addressing. Ideally, the current maintainer would allow someone to take over this repository, but that does not appear to be realistic.

To make any improvements, the only realistic option appears to be forking the project. It's in our best interest to unify the community around a single fork, so we can benefit from network effects, and so all improvements can be upstreamed into a single codebase.

I can take the lead on this. I'm happy to fork the repository and publish it to the marketplace. But I won't be heavily invested in the code. I would rely mostly on the community to implement, review, and test improvements.

It would be better for the project to be led by someone who is interested in making more significant contributions. Is anyone actually interested in working on this code, and willing to commit to long term maintenance?

[karlhorky]

CCing some other contributors from the past too:

• @bbugh
• @hjfreyer
• @meelkor
• @bradleyayers
• @mk12
• @JimmyZJX
• @GSGBen
• @MadLittleMods
• @tomshafer

[szh]

Does anyone want to start a fork?

[dnut]

No one has nominated themselves in the two months since I proposed forking, so I forked it here: https://github.com/dnut/Rewrap

I haven't made any code changes yet, but I plan to spend time on this next week, since I'll be off work. The first thing I'll do is publish the identical extension to the marketplace under an account that I have control over. Then, I'll work on #389 and get that published in a pre-release version.

I made some changes to the branching. In stkb/Rewrap, stable is the default branch, which is confusing because it is not the development branch. It only represents the latest stable release in the marketplace. Unfortunately, since it is the default branch, all of the PRs use stable as the base branch. But actually those PRs should all be merged into the branch that's used for development, which appears to be the prerelease branch.

To resolve this confusion, I've created a master branch as the default branch, which I will use as the primary development branch. The stable and prerelease branches now only represent the respective marketplace versions.

I won't have time to review and test all 14 of the PRs in this repository any time soon. I'll start chipping away at it, but it's not my top priority. I suggest you to create a new PR in my repository if you'd like to prioritize a particular change. I would also appreciate contributions to code review and testing.

[dnut]

I published the extension as "Rewrap Revived" with the same release and pre-release versions.

https://marketplace.visualstudio.com/items?itemName=dnut.rewrap-revived

I suggest installing the pre-release version so you can identify any bugs and report them so they don't make their way into the stable release. If you report any observed bugs, you can switch to the stable release and rest assured that the bug won't appear there.