Re: [Axiom-developer] axiom: [426] branches/wh-sandbox

[Alfredo Portes]

> One thought might be to include certain "metadata" in the chunck
> structure which could be used to automatically add citations and
> credits - if we make an emacs mode (say) that when it reads an Axiom
> pamphlet parses the metadata and tracks what is changed - then each
> chunck knows who changed it and who didn't, and can automatically
> produce citation links on that basis (for example, a code block that
> survives unchanged through 4 major pamphlet revisions need only refer
> to the original, since that is where it came from.)  Maybe one of the
> many source code management systems we have available could even
> automate this feature based on commit diffs and who is commiting?  Then
> the question of "who wrote what" can be quickly and definitively
> answered.  If desirable there could be some "primary authorship"
> decided based on how much of the current code is new compared to
> previous versions.  Peer review could be used to override abuses of the
> system (for example, making unnecessary and trivial changes in enough
> parts of the code to claim primary authorship.)

I know that this is not the current development process, but I think
Tim has explained before that in the pamphlet, when you correct
errors, modify or add, you should leave the old code as not used chunk
and add the new code explaining how it improves the old code, and it
serves like Gaby said to keep a history of the changes.