Forum: Weblog comments

Preserving Software - Feedback...

AutorBeitrag

KaiRo

Webmaster

zitieren
Preserving Software - Feedback Requested!

Dieses Thema wurde erstellt, um Kommentare zu einem Weblog-Eintrag zu fassen.

Damit zusammenhängenden Weblog-Beitrag anzeigen
16.05.2013 23:46

thp

zitieren
Discussion threads and bug tracker entries
"Would this need to go as far as preserving discussion threads and entries in bug trackers?"

Discussion threads: Probably yes. My initial thought was to just preserve the -devel mailing list (development topics), but a -users mailing list (end user questions and support) might just be as important, and serve as a fallback to look for answers where the real end user documentation (user manual, etc..) doesn't provide a good answer.

Bug tracker entries: Definitely. Imagine a source code comment line that says "We need to reevaluate the query here because of bug 4711." - people studying the source code will have an easier time understanding decisions and motivations if they can read the history of a bug report (and maybe alternative tries at solving the problem and why the alternative solutions weren't chosen).

Ideally all URLs referenced in source code comments should also be mirrored (wayback machine style). Imagine a tricky algorithm that is based on some scientific paper or article somewhere on the web (with link in the source code) - getting access to that paper/article might be very helpful (or even essential) for understanding the algorithm's inner workings.
17.05.2013 09:46

Liz

aus San Francisco

zitieren
Preserving data and environments
This is great. I love your answers and especially making sure that the archive project tries to license the archives in as free and open a manner as possible.

I also agree that bug trackers, forums, and comments will be useful for future research, for people who want to redeploy software on future platforms, or for historians and data scientists. Thanks so much for reporting on this process!
18.05.2013 06:19

Antwort verfassen