Wiki To-do list

Please describe error and omissions in the BOINC documentation here.

Missing information (or requests for documentation)

• UpdateVersions mentions adding an <app_dir> tag to config.xml, but it's not listed in ProjectOptions (does the tag still exist?).
• Where is the format of global_prefs.xml? I want to link it from ClientSim#input_sim_prefs. I see many pages with related info, I don't know which one is right or correct: PrefsImpl, GlobalPrefs? (doesn't show XML format), PrefsOverride, and bottom of ClientFiles.
• It may be useful to have a new page (MigratingServers?) explaining how to migrate a BOINC project to a new server.

Out of date information

• PrefsOverride is out of date, as it says on the page itself. Somebody should go check the code for what the current prefs format is...
• Implementation notes are most very outdated.
  • An updated ClientApp? may help create a library to allow Java applications on BOINC; basically porting the BOINC API to Java.

Minor corrections

• ManagerAdvanced? could have some new screenshots. Current ones show glitches on the rendering of menus. Also it's probably better to keep the screenshots as attachments to that page, instead of stored somewhere else on BOINC server, that way contributors can change them.
• AlphaInstructions has missing links at the very bottom. It says "see here and here" but words aren't linked.
• JobIn needs similar work to BackendState: reformatting using headings instead of that table mess. I reformatted JobIn using definition lists. I think it looks better than with headings, but we can't link to individual attributes...
• minor correction project list about date of LHC first turn-up - according to ​this press release the machine will not "see" first-light until May of next year.
  • This isn't part of the Wiki.

Misc

• PythonMysql had been converted from the original .txt. I recently "wikified" the page, since it was just plaintext copied verbatim. It probably needs some cleanup, and checking if the information on it is still correct.
  • Answer: With recent distributions you won't need this page anymore. I always used the stable packages (usually: python-mysqldb) provided by each distro and got no problems. ChristianB
  • Other pages need to be updated to say Python DB can just be installed that way.
• Would it make sense to move DevProjects stuff into Trac tickets marked as 'Task'?