|
From: Nicholas N. <n.n...@gm...> - 2023-03-22 23:09:11
|
All the Rust projects I work on use GitHub, and in terms of usability and productivity it's miles ahead of how Valgrind development works. If I were king of the world here's how I would drag Valgrind's development practices forward by 10-20 years. - Move the repository to GitHub. Require all changes to be done via pull requests, with no direct pushing. - Set up some CI testing via GitHub Actions. Require that all pull requests pass these tests before merging. - Lots of projects require a review approval before a pull request can be merged. But that might be too hard for Valgrind to start with, given the small number of active contributors. - Switch from KDE bugzilla to GitHub issues for bug reporting. Not sure what I'd do with existing open bug reports, whether it would be worth importing them to GitHub issues somehow or not. - Use auto-formatting tools, such as clang-format. (Possibly even moving from 3 space indents in C code to 2 or 4!) - Change the docs from that XML-based thing we use (groan) to something nicer, probably involving Markdown. - Website: not sure... a lot of it could be naturally hosted on the main GitHub page. It might be nice to still have valgrind.org, though, but perhaps greatly stripped back. I understand the concerns about GitHub and commercialization, but I also worry about Valgrind's future viability if it doesn't attract some level of new contributors. The Linux kernel will never have that problem, but I suspect lots of GNU projects also face that risk. Nick On Thu, 23 Mar 2023 at 08:19, Paul Floyd <pj...@wa...> wrote: > > > On 22-03-23 21:31, Nicholas Nethercote wrote: > > Thanks to Paul and Mark for a couple of small fixes to my commit. > > > > Yesterday I was idly dreaming about the quality-of-life improvements > > that would be available if Valgrind was hosted on GitHub: > > - ability to upload commits ahead of time, in a fashion nicer than > > "attach patch to bugzilla" > > - ability to do reviews > > - CI support for pre-merge testing runs > > - easier entry for newcomers > > > > Does sourceware.org <http://sourceware.org> have support for any of > > these things? > > Hi > > GH does have a lot going for it, and when they add code browsing it will > be even better. One concern though is their owner and creeping > commercialization. > > As far as I know, a lot of GNU projects and Linux still work mostly by > by patches sent to mailing lists. > > One other fairly common system is phabricator (used by LLVM and FreeBSD > amonst others). However, the company that developed phabricator closed > down so I don't know where that is going (there is a fork). FWIW FreeBSD > is increasingly using GH. > > A+ > Paul > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |