Question: relation between this repo and virtualagc? about apollo-11 HOT 3 CLOSED

See #38 for prior discussion.

I was unable to contribute much from 2017 onwards (from being one of the most active proofers) as I was at university, which I have finished this year and will be starting to go through the proofing issues once I've dealt with maintaining my other projects I've neglected over the years.

from apollo-11.

@lurch Regarding #690, the Virtual AGC Project already provides colorized, hyperlinked HTML forms of all known-surviving AGC code. For example, the HTML for Luminary 99 is here, and the HTML for Comanche 55 is here. Perhaps #690 provides some advantage over the HTML already provided; if so, I admit that I haven't examined the PR closely enough to determine find out.

Historically, the AGC code transcriptions in this repository originally came from the Virtual AGC Project transcriptions, but prior to the many Virtual AGC Project corrections you've discovered are present in the Virtual AGC repository now. From the Virtual AGC side, the only interest is in the accuracy of the transcription: there is no interest in maintaining a clean room. So, speaking just for the Virtual AGC Project, PRs for problems in Virtual AGC transcriptions are certainly welcome. (I have no insight as to whether PRs in the other direction are welcome.)

from apollo-11.

Regarding #690, the Virtual AGC Project already provides colorized, hyperlinked HTML forms of all known-surviving AGC code. For example, the HTML for Luminary 99 is here, and the HTML for Comanche 55 is here. Perhaps #690 provides some advantage over the HTML already provided; if so, I admit that I haven't examined the PR closely enough to determine find out.

It's just displaying the scans in a quicker-to-navigate way. As opposed to opening multiple tabs or constantly editing the address bar while going through the pages to check for transcription issues.

(I have no insight as to whether PRs in the other direction are welcome.)

Those are welcome too.

I think the overall goal as of now is to finish going through the open proofing issues and once that is done diff against Virtual AGC (with the scans being the source of truth) to make sure we don't accidently re-introduce typos that were fixed on Virtual AGC but missed by us. Of course, diffing against Virtual AGC can be done in parallel to the continued proofing of the scans, so I don't mind either way.

I still need to check (locally) if git merge --allow-unrelated-histories from #38 will accomplish what we desire with maintaining commit attribution to chrislgarry/Apollo-11 and Virtual-AGC/Virtual-AGC contributors though.

from apollo-11.