i dont really intend to argue for either workflow being better or worse - but mainly to point out for practical reasons that for the majority of potential new contributors (especially those younger than 30) will never accept the patch-centric workflow and they simply will not contribute to GNU projects which is a loss for everyone
certainly handling all changes manually has it's merits but on the other hand, there is nothing preventing a maintainer from converting a merge request into a patch themselves that they could patch by hand if they wished to and then commit back to git in fact - now that i just looked a bit closer it appears that libreJS is ALREADY using github for precisely this purpose https://git.savannah.gnu.org/cgit/librejs.git/commit/?id=a1be2ee58c0f35e2434e073d1424b27c1ac82230 https://github.com/nikolas/LibreJS/pulls?q=is%3Apr+is%3Aclosed now that ive noticed that - i suggest to Nathan that you could also fork that github repo and send a PR via github if you are more comfortable working that way - and perhaps nikolas will respond on github and accept your contributions that way
