Perhaps then the community can still forge ahead with a Git repository to share ideas and bug fixes and suggestions for improvements, which you can feel free to incorporate or ignore, and then the community should just baseline their Git repositories off of the arc<(max n)>.tar?
Yes, exactly. The Git repository is terrific resource as a place to conveniently store everyone's patches, but of course some patches may be "bad" (by one criteria or another), and that is OK (good even) for its purpose.
I'm running Linux, and so date was broken and thus so was the web server, I looked in the repository and was happy to see someone had a fix, and I didn't even have to read the date man page (lazy me!)
So, just like you say, Paul's canonical releases of arcn.tar and a community repository (for good patches, bad patches, experimental patches, weird patches...) are both useful.
"... I'm running Linux, and so date was broken and thus so was the web server, I looked in the repository and was happy to see someone had a fix, and I didn't even have to read the date man page ..."
Yes. When projectileboy said "the Git repo that's been created", I assumed he meant the one you just linked to (I don't know of any other), which is where I found the date fix.
