Dear Stefan, > This sounds awesome! I am the original developer of this whole thing. thank you very much for developing gerbv, it’s utility cannot be overstated! > I have actually been pondering exactly this move for a couple of months, but >I'm happy you beat me to it. that’s a relief! Creating a fork is sometimes seen as a hostile action, but this is definitively not the case here. I couldn’t find your GitHub handle, but I’d be happy to invite you into the gerbv GitHub organization. > Considering all the tools available today there are probably many and great >ways to improve the code base. For instance, I took pride in running valgrind >now and then to avoid memory leaks. this is actually one of my medium-term goals :-) first I want to get the code to compile with -Werror and then get the tests running again / add new tests for patches. > But baby steps... I think this is a great step to at least being able to >start accepting and incorporating all the patches that floats around out there. looking forward to a new future for gerbv! Kind regards ooxi >Воскресенье, 29 августа 2021, 20:13 +03:00 от Stefan Petersen <s...@ciellt.se>: > >Hello Violet! >This sounds awesome! I am the original developer of this whole thing. I have >actually been pondering exactly this move for a couple of months, but I'm >happy you beat me to it. I saw that you already have made great progress on >GitHub like adding CI and a nice web page. >I think this is precisely the injection gerbv needs by starting a more open >development and accepting changes easier and more broadly. When I stopped >working on gerbv git was a glimpse in the eye of Linus Torvalds. But with all >the infrastructure with GitHub et al hopefully makes it easier to run this >project. >Considering all the tools available today there are probably many and great >ways to improve the code base. For instance, I took pride in running valgrind >now and then to avoid memory leaks. But as soon as I left a bunch of Python >developers rewrote a lot of code because "it looked bad" and "didn't like the >code" and thus created a lot of memory leaks. >But baby steps... I think this is a great step to at least being able to start >accepting and incorporating all the patches that floats around out there. >Best regards, >/Stefan >On 2021-08-29 17:13, Violet Land via Gerbv-devel wrote: >>Hi everybody, >> >> >>I’m an avid user of gerbv and have also integrated libgerbv into my workflow. >>Unfortunately, as others on this mailing list have notices, the development >>of this project has stalled. >> >>I therefore decided to create a gerbv GitHub organization [1] and invite all >>interested parties to join. CI based on GitHub Actions is already running and >>binaries for Ubuntu, Fedora and Windows are published on >>https://gerbv.github.io/ >> >>My next steps will be to apply bug fixes from SourceForge and the Mailing >>list, which I can verify myself. My hope is to revive this project and have >>pull requests from other developers. >> >>This is a friendly fork and I invite everybody, especially the original >>developers to join :-) >> >> >>Kind regards >>ooxi >> >> >> >>[1] https://github.com/gerbv >>_______________________________________________ >>Gerbv-devel mailing list >>Gerbv-devel@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/gerbv-devel >> >-- >Stefan Petersen >Ciellt AB >Läckövägen 23 >SE-121 50 Johanneshov, SWEDEN >Tel: +46-733-627526 >Web: http://spe.ciellt.se/ > >_______________________________________________ >Gerbv-devel mailing list >Gerbv-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/gerbv-deve l
_______________________________________________ Gerbv-devel mailing list Gerbv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gerbv-devel
