User:Sardisson/To Do

Things I need to do for cb.o/support, cb.o/development, or triage:

cb.o/support

• All the Support updates/fixes from my sticky note

support/Hidden Prefs

• "this is how you make all cookies expire on quit"
  • "except for existing cookies and whitelisted sites"
  • "Setting network.cookie.lifetimePolicy to foo will cause Camino to automatically accept all new cookies and keep them for the duration of the browser session" - "until you quit Camino"

• link to mZ kb permissions.default.img doc

• inline autocomplete: http://forums.mozillazine.org/viewtopic.php?p=2134006#2134006

• chimera.log_js
• camino.accept.lang

• http://www.mozilla.org/docs/end-user/keywords.html

• user.js plain text "creating"; not running

support/Docs

• annoyances/#hostperm: link to new hostperm.1 mZ kb article
  • create hostperm.1 if needed; edit when not running

• security: p12 certifs (restore, not import)

• bookmarks:
  • To make the newly-imported bookmarks appear in the bookmarks menu or bookmark bar
  • bm import->move bm from collection to bar

• passwords in FAQ - ????

support/Bugzilla FAQ

• Revisions to the Bugzilla FAQ
  • QA:Bugzilla:Searching_For_Dupes
  • Instructions for tasks QA commonly asks reporters to do
    • Fresh profile

    (Essentially, cb.o support needs a Camino version of this)

    • Screenshots in JPG or PNG, not PDF or TIFF
  • "pay attention to your bug; we will ask you questions"
  • new "Before filing bug" section
    • no UA spoofing
    • use latest version/nightly from last 2 weeks
    • Fresh profile
    • Check in Fx
    • QA:Bugzilla:Searching_For_Dupes
    • plus the crash/sample stuff there
  • “Bugzilla is not a forum” - Behave! Link to https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
• Put the Bugzilla FAQ in the Support sidebar (raise visibility in support vs in development)
  • Move some bug-reporting stuff from dev/ to sup/

cb.o/development

• Development:Good Bugs and Projects

  See also Development:Home Page

• dev#report_bug - old url to bugz faq
• dev/build - link to tarball

cb.o/other

Relnotes

• relnotes: We want to know what you think! Be sure to contact us and let us know what you think. ????
• Each header should have an id/anchor for easy linking

Features

• features/ has old links into docs

Community

• access keys on community sidebar, but not on blogs.cb.o

• /community/ :"community-related" ?

  Welcome to the community center of the Camino project. Here you will find a gathering of Camino related news and other bits of information by its developers, keeping you up to date with every step forward.

Home

• js switcher img
• CSS validator: <http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww-stage.caminobrowser.org%2Fsupport%2Fdocs%2Fdownload%2F>

QA Stuff

add these to relevant QA pages when Sam starts them

• Development:Keywords & Status Whiteboard
• Development:Bugzilla:Searching_For_Dupes
• [01:06am] smorgan: Clean profile is supposed to be a narrowing down tool, not a magical remover of bugs. Only corrupt/invalid profiles that appear to be caused by users mucking around should be consider ignorable.