Cretezy
Proposal: Fork repository to speed up development
This is a proposal to fork the repository to speed up development and make the merge process more smooth.
Problem Currently the repository has 1 active developer who can approve PR (istudyatuni). It is only possible to approve a PR via a squash commit, not via a merge commit.
Desired situation
- At least 3 active developers with authority to approve PR. This will make it more likely that pull requests are responded to quickly.
- The ability to do rebase merge commits instead of only squash commits on PR. Smaller commits makes it easier to follow complex refactoring.
Proposal Within the last 6 months, the contributor with most additions is istudyatuni. I propose that his fork is made the official development repository until Cretezy can share his future plans for the project. The issue list should be kept in the original repository (no issues on the fork), to ensure continuation.
Furthermore, I propose to invite developers with more than 100 additions/removals within the last 6 months to the role of collaborator. This should give them the ability to accept PR and do rebase merge commits.
Process I would prefer to keep the repository under Cretezy control, therefore I contacted him via mail with this proposal a week ago, but he is busy with other projects. A week is not long time, so posting the proposal here is primarily to gather the community opinion.
I would like comments on this proposal. Do you think it is a good or bad idea? Why? Please give it an up or down vote emoji.
Another issue is that only Cretezy can update crates.io: https://crates.io/crates/lazyjj (still stuck on version 0.5.0).
I'm in favor of getting things done faster, but moving development over to another repo yet still being unable to publish to crates.io seems like the wrong approach. I'd be more in favor of one of:
- granting publishing rights to more people
- creating a lazyjj org (incl. more people that may publish to crates.io)
- a true fork, as much as I'd like to avoid this one it seems better than working somewhere else and still being unable to update crates.io
