zimmski
commented
1 year ago 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
Felixoid
agirlnamedsophia
Hi everybody! For what I've seen this past few months, seems that
go-mutestingis 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-mutestingcan 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!