Skip to content
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

Is go-mutesting dead? Proposal for fork #100

Open
facecrusher opened this issue Jul 5, 2022 · 5 comments
Open

Is go-mutesting dead? Proposal for fork #100

facecrusher opened this issue Jul 5, 2022 · 5 comments

Comments

@facecrusher
Copy link

Hi everybody!
For what I've seen this past few months, seems that go-mutesting is abandoned. I honestly feel like this is a very good framework for mutation testing in Go, and it would be a pity to just throw it to the garbage.

I'm wondering if among the people who use this repo and the ones who have contributed we can build a community, and perhaps make a fork where we can define a roadmap for the tool and start making regular updates. I think that with a little love, go-mutesting can become a powerful tool for go developers.

I know there's a few more updated forks out there (I'm thinking avito-tech) but again, it's not clear if they have a defined roadmap, or if they are still actively working on it (last updates are from about 6 months ago).

So I'm leaving this question open for folks who want to collaborate to post here, so maybe we can work something out. Thanks!

@zimmski
Copy link
Owner

zimmski commented Jul 12, 2022

Hey. As many might have expected i am super swamped with my "day"-job at @symflower and having a kid takes up all my private time. I did not work out to do open source that is not part of my day job in my free time, i am sorry for that but that is just how open source sometimes works. HOWVER, I will discuss making go-mutesting part of the maintenance of Symflower in the next investor meeting (cannot decide this on my own, but there should not be any blockers here). The idea is that Symflower does the maintenance during workhours and with its employees (e.g. reviewing PRs, doing changes, issue grooming, ...). Goal for me would be to grow the community and technology behind go-mutesting for regular mutation testing, while making the vision of Symflower come true also for this project: there is a better technology, where we can do a MUCH better analysis than what go-mutesting does, and even faster.

What do you think?

@fbustamant3
Copy link

Honestly, this is great news. To have a team leading the way while the community collaborates to add more functionalities, seems like the way to go.

@fbustamant3
Copy link

Hi! Just checking if there are any news on this? 👀 @zimmski

@Felixoid
Copy link

Hi dear @zimmski, any news regarding the repository's state?

@agirlnamedsophia
Copy link

Very interested in this library as well - will it be maintained by your team @zimmski ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants