Difference between revisions of "User:Sardisson/To Do"

From Camino Wiki
Jump to navigation Jump to search
(→‎support/Bugzilla FAQ: move this section somewhere more high-profile)
 
(3 intermediate revisions by the same user not shown)
Line 46: Line 46:
 
* passwords in FAQ - ???? (what the heck was this?)
 
* passwords in FAQ - ???? (what the heck was this?)
  
===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 [http://kb.mozillazine.org/Standard_diagnostic_%28Firefox%29 this])
 
*** CUPS debug log (rare)
 
*** Console.log (rare)
 
** "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
 
*** Link to [https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html bug-reporting guidelines] ??
 
** When reporting a bug (beef up existing instructions)
 
*** '''File using the build in which you experienced the bug'''
 
*** no UA spoofing
 
***: Some sample text [https://bugzilla.mozilla.org/show_bug.cgi?id=337402#c3 here]
 
*** Attach crash log or sample (already in the FAQ)
 
*** Screenshots in JPG or PNG, not PDF or TIFF
 
** '''“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==
 
==cb.o/development==

Latest revision as of 15:10, 2 July 2007

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"
  • chimera.log_js_to_console
  • camino.accept.lang
  •  ??? pac override (already on proxies page; why duplicate it)
  • user_pref("browser.display.use_document_fonts", 0); (font-face, not size)
  • user.js plain text "creating"; not running
  • bookmarks keywords: just a ref to the extensive documentation in support/docs/bookmarks

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
    • http://www.mozilla.org/docs/end-user/keywords.html
      Maybe put this in sup/docs/bookmarks since I'm editing that anyway?
      With a reference to it from the keyword.enabled entry? NO
    • Documentation on sorting?
      Implement bookmark sorting (really arranging) in Camino.
      • Selecting a single folder will sort its children.
      • Selecting two or more items will sort them together.
      • Holding down the Option key will do a deep sort of all selected items.
      • If nothing is selected, the current collection is sorted (if allowed).
  • passwords in FAQ - ???? (what the heck was this?)


cb.o/development

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

QA Stuff

add these to relevant QA pages when Sam starts them