Support Team Leader's stuff
Specials, one-offs, projects:
- Develop the data retention practice as per SP.
- Werner's mail/thread "Support mailbox structure" 20091205.
Routine, all the time, continuous:
- Recruit: Triage, SE
Assurer => Triage => SE => CM => Arbitrator
- transition the Triage members into SE
- review documentation:
- respond to board
- prepare annual team report for AGM
- support to Arbitration
Watch the Support -> arbitration filings bridge
Longer term questions, cleanup, lower priority:
- mailing lists and privacy:
- make cacert-support a PRIVATE or PUBLIC forum?
- change the name of cacert-se to free up -se (sweden) ...
- changed to cacert-support-engineer
- change SP
- for ABC ?
- for Triage?
- Create the Support Challenge
- develop the fiddle process? Shift to CATS? Another way?
- Deprecate the mailbox.
also see DataRetentionPractice.
- cacert-support -- walled garden?
- direct and help to establish the cookbook or FAQ for the Helpers.
- Recruit to Triage.
- push the message to other t/ls to recruit for Help Team, etc.
Support/Triage needs you!
Requirements for Triage Team:
- client cert in your email client (MUA) and browser
- has lots of tiny slices of time available
- comfortable with webapps like OTRS
cool with reading English
- comfortable with writing basic English
- advantage in as many other languages as we can get
- organised, thoughtful, efficient
- understands/agrees basic thrust of CCA, DRP
- agrees to SP
- understands CARS
- got IRC
We need more people outside Central European timezone.
- monitor the selections, and confirm their correctness. Give feedback.
- keep the speed up.
- Set target. 1 hour?
Recruit people for ABC => SEs, or for CM role.
- The primary place to recruit Triagers would be from Help Team.
- on team changes, watch mailbox handover
- whether Assurer (wp)
- personal recommendation
- small print (wp)
point to doco: Support/Triage (wp)
- point to IRC: se (wp)
- point to fiddle mini-C (wp)
- do Support-1, Triage-1 and Triage-2
- need s/mime encryption, may get a community address (wp)
- Send the Welcome Pack (==wp)
- intro to team
- bring into OTRS, #se, cacert-support-engineer@
- try a few cases
- add post-capable to cacert-disputes and cacert-support-engineer
- chase email address + s/mime, and wiki page.
Requirements for SEs:
- good grasp of CAcert in general, overall
good with writing English
- other languages in written form an advantage
- understands/agrees CCA, SP, DRP
- is under SP
- good with diverse interactions, can interpret complications across borders
- has some (a few) larger chunks of time available, maybe an hour a day.
- flexible, "completer"
- has completed term-of-service as Triage
- has done Triage-3, Support-1
- PG's list
- Webinterface Handling
- Handling Various Crypto-Related Application (Browsers, email clients, VPNs, OpenPGP, GnuPG, ...)
- Understanding of certificates, the related standard, ...
- Understanding of Security, Security-Policy and Guidelines, Social-Engineering Resistance, ...
- CAcert's offerings, services, products
- CAcerts organigramm, knowing who is responsible, who to contact
- to monitor the actions taken, and confirm the instructions. Coach and discuss.
- keep the quality up, not the speed
- watch for rudeness, brushoffs
recruit from Triage => SE
push SEs => CMs.
Please file DISPUTE to request Arbitrated Background Check over Santa Claus, known as St Nick <presents@co> . He is currently working as Triage within Support Department.
The direct result is to propose him to board for the potential role of Support Engineer, as covered by Security Policy 22.214.171.124. However the ABC can be seen as broad and independent of Support work.
- whether Assurer
- personal recommendation
- small print
point to doco: Support/SE
- point to IRC:
- point to mini-challenge and full challenge when written
- add to:
When handing over the job, run through this checklist.
Maintain a list of team participants at Support/Team. Early job: send an individual ping to everyone listed to confirm participation and aliveness.
- The application administration rights for OTRS:
- "admin" currently for Michael (STL) and the admins below.
- underlying application (SSH?) is with Mario (otrs-admin) and Nick (backup otrs-admin).
- wiki page admin rights over the Secure pages for SEs.
- Mario (wiki-admin), Michael (STL).
- The support@co Mailbox needs to handed over, also when triage people leave.
- Actually it is being deprecated, so the task is also to clean it up. See the Data Retention project.
Need visibility (subscribe) over these:
- support mailing lists:
cacert-support mailing list so as to see the action, help any major confusions, and identify some better practices
- SE, triage, help, ...
cacert-disputes mailing list (case-management list) so as to confirm that fowarded disputes are not being dropped.
STL should own and admin the SupportEngineerGroup page, and manage the private pages for SEs. Search Text on that page name to find. Use this sparingly as usage of access controls is generally a bad thing. Ask wiki-admin@ for help.
Support uses the chat room "se" for support people. Generally, Triage and SEs are on there only, plus a few invited guests.
Currently it is not set up as a proper secure channel.
Liason is conducted with
- Arb team somehow (currently through u60 being on Support forums).
- Board (by Iang being member).
- OA team (Mario).
intro to support, how to help on the open forum
intro to triage, outside-basics
messages, buckets, channels
preparing to enter Support Engineer work
Done by Iang under his SO Period
- got control of mailbox
- investigated the folders
reviewed styles of messages going out, in Support/Triage
reviewed SP as against triage plan, mailed out to policy, etc
Guillaume's template emails for SEs in their page
Training on system operation for SEs dox in Support/SE/Manual from session with PG 20091120 MQ.
reviewed / updated the Guidelines for Support of Arbitration
- started on fiddle mini-C questions for Triage and for Support
- documented the process of new Triage
- bringing in the first people: Neo + Werner.
documented the Triage -> help forum question.
- Neo wrote the sieves. Turned my filters off.
- create a #se in IRC.
- created cacert-support-engineer list
casa + JS => Triage
- long debate with Arbitration to get mails flowing back and forth between Arbitration and Support. Still not resolved.
- debate with treasurer about how to deal with Payments.
- Paypal issued debated, dispute initiated.
- intervened to stop breaches of SP.
- reported to Board 20091206
- Brought in new people:
- JS, added
- Jm3 halfway?
reviewed Security Policy
- proposed change to add appointed assistants of channels only.
developed the Support/Team documentation and structure
figure out the triage thing Support/Triage
- added the password practices page
- wrote, proposed, added the community help forum page
- initiated review of issues.co by team as t/l is too busy and can't tie his own shoelaces
- favourable comments from Marty1
- Support reported to Board.
- 3 ABCs done.
- reviewing Support fiddle mini-C questions
- reviewed the ABCs.
- proposed in agenda/motions to board.
- Support reported to Board, Board approved 3 new SEs.
- notified, added as per checklist below.
- Started Triage recruitment again.
- Triage in progress: jm3, Faramir, Fred?
- Adding Dominik.
- Mailed out for ideas on T/L.
- OTRS / issue is moving. Now handling the tasks as primary method.
started the DataRetentionPractice from Werner's mail!
- Board / neo is now T/l