My Google-apps terms

Problems

Google's naming (e.g., Google-apps, Google-docs, Google-sites) does not capitalizes first letter (i.e., otherwise we have to write fully "Google-xxxx") and also names them in plural.  This is not practical in documentation when we refer particular source in its service.  Worst of all is GDocs text document that its term is also too generic.

For examples:

• "... refer 'Project-X proposal' GDocs document":  someone might wonder: is it the 'document' type or another document type?
• "... posted in Google-sites 'Project X' under section ...", or "in GSites 'Project X' ..." and anyway neither of them appears grammatically correct about plurality; or we have to write longer "... Google-sites site 'Project X' ..."

My terminology:

• GDocs, GSites: Google docs/sites services
• G.document or G.text, G.spreadsheet, G.presentation, G.drawing: document of Google-docs's native types (i.e., not an uploaded file).
• GDocs.xxxx where xxxx is either of text, spreadsheet, presentation, drawing: another alternative as GDocs.text looks less confusing than G.document or G.text.
• Note that 'text' document does not mean plain-text file (.txt) which is so familiarly perceived.
• GDocs file: GDocs uploaded document/file, not converted to native type.
• G.site: a site in GSites system
• GSites page/comment: page or comment in a G.site.

How to collect emails for sharing away, in GMail

a.k.a., for forwarding :)

Method 1: Forward under a common subject

• Define common subject for each email thread (ex., "FYI: Cyber magics").  Optionally assign label "++" to ease locating the mail thread later.
• Copy and paste into the thread's new reply and review appropriate recipients when send.

Method 2: Use label

Simply forward the email, and then assign label.  Here is recommendation: Tags for FYI & Forwarding.

My bulleting

How I mark bullets in planner/lecture books.  "When type" is nothing by this time.  I try to match to appropriate-looking characters on keyboard -- just in case.

When type	When write	Use for
_	[_] square	to-do entry: needs later checking for progress/completion.
=	/\ normal triangle	milestone, scheduled-ahead event: may need checking
+	\/ revert triangle	incident, interruption
-	> right-arrow triangle	normal entry: doesn't need later reviewing.

Progress marking for to-do & milestone entries:

• . (dot) = Started: put at lower-left corner so that it can be / or X later.
• / = Done
• X = Aborted, canceled.  Also compare with '0' (zero).
• - (dash) = Skipped: neither action nor decision yet.
• \ = Moved to another tracking system
• ^ (north-east arrow when write) = Forwarded/postponed: same system (such as another page)

Solutions to log chat history

Reason: Although Y!Messenger provides option to save chat history, it saves in local machine: i.e., we don't get chat messages received while being with office PC when open home PC at night.
(I no experience with recent Live Messenger)

Solutions
a) If a message is short, tweet direct message.
b) If Twitter is insufficient (length limit), post to a personal blog.

My top feature requests to Google GMail/GCal

Re: Rosemary, "Google Pilot: Survey on Top 10 Feature Requests" >> https://vovici.com/wsb.dll

• Remove calendar invitation from the Inbox once it is added to calendar
• Ability to see size of an email
• Ability to add email addresses, which are not in the My Contacts list, to a group manually
• Ability to request a return receipt when a recipient has opened your email
• Setting a priority on an email that is sent out
• Selecting and forwarding more than 1 email at a time
• Ability to delete an attachment from an email or conversation thread while leaving the rest of the email(s) intact
• Access to the global directory/shared contacts in order to change phone numbers or other personal information
• Ability to send a chat to a group of people
• Better use of space on right side of email window by moving menu options (New window, Print all, etc.)
• Rich text editing capability for calendar entry 

Ending comment
Header part would be better optimised:-
- Unnecessarily lengthened: "Firstname Lastname <firstname.lastname@domain.com>" -- any Labs' tweak to display shortname/nickname?
- [show details] would be icon button to save space.
- Or better 2 lines to cover necessary brief.

My tweeting shorthands

(Now published to FrontierDigest)

My hashtags

• SOM = same-old/so-often/still-ongoing mistake(s)/mistaking/misunderstanding -- complementary to FAQ
• FFA = frequently-forgotten answer(s) -- complementary to FAQ
  
• down = system-down incident
• mailed = already (e)mailed.  Same idea as Yammer's #joined.

Financial accounting codes

BBBtNNN

• BBB = bank name
• t = type
• NNN = additional names such as branch, programme

Bank-account types

• - = savings (dash denotes general/default type)
• % = fixed deposit
• $ = special savings

My Gmail SuperStars

1. yellow-star:  Normal, default -- it is Gmail native flag.
2. green-check:  What has been done, replied, responded. Normally when a topic is routine, scheduled, or followed up.
• Another implication is to indicate mail which I expect for replying, and when it comes back then it's my turn to review: i.e., this icon indicates "what I'm waiting for" -- mail that needs reviewing (and may even expect my next action!).
3. blue-info:  Specific information -- require some further attention/action.
4. purple-question:  Need further discussion, finding-out.
5. orange-guillemet:  To delegate/assign to someone else.
6. red-bang: ATTENTION, IMPORTANT

Associated implication (normally in multiple inboxes or quick links)

• 'Reports & info' =  l:.report OR has:green-check OR has:blue-info
  
• 'Reports? (inbox)' = in:inbox subject:(report OR status) OR has:green-check
• ...
  

Others that I don't use

• Other stars (red, orange, green, blue, purple): Let be simple, one star is enough. These colours are also redundant with others.
• yellow-bang: default star is already yellow.

My mail tags/folders

friends2
9/23) = friend friend = friend's friend: friend of friend.
For social-networking catagorisation.

ROM
9/25) Review of operation/management
Others in consideration
- MOR, MORe: management/operation review
- MM: management memo

run (.run)
10/1) From classic computing term. This is because using "done/end" is not practical in Gmail: an already done/end mail can be later replied and then returned to Inbox (and not done/end yet) again. Note that "run" is also the past-participle of same "run": i.e., no matter it is returned/restarted, it was run anyway :)

Would we walk on left or right?

เราควรเดินชิดข้างไหนบนทางเดินสาธารณะ?

Left

1. ตามการเขียนหนังสือ -- ถ้ามีป้ายหรือประกาศข้างทาง จะอ่านได้สะดวก
2. ตามระบบจราจร
   

Right

1. เวลาอยู่บนทางเท้าข้างถนนจะเห็นรถสวนง่ายกว่า
   

Otherwise

1. ควรใช้มือไหนจับราว(บันได)?