. '''To Software''' '''[[Software|Software]]''' - '''To Software-Assessment - ''' '''[[Software/Assessment|Software/Assessment]]'''

----

= Minutes of the MiniTOP on the 2010-10-19 =

== Setting ==
The MiniTOP will be held via telco --(or irc)--  20:00 CEST

Attendees: Martin, Markus, Michael, Uli

== Action items from last meeting ==

== Topics ==
 * State Testserver Update
  * Current Patch on Testserver: [[https://bugs.cacert.org/view.php?id=876|Bug# 876]] 
   * "0000876: NRP-DaL to be removed immediately NRP-DaL Link"
   * verification documentation by transfer patch to critical team after review by 2nd Software-Assessor
  * Preparing "Thawte" patch [[https://bugs.cacert.org/view.php?id=827|Bug# 827]]
 * Andreas/Markus: signer deployment - Updates ?
 * Automated testing system
  * Andreas, Magu, MSchiffer
 * next meeting: Tuesday, Oct 26, 2010 ?

== Minutes ==
 * Software-Assessors current situation
  * There are currently 3 SA nominated
  * Only one is active, so the 4 eyes principle doesn't work, other 2 had not picked up the task yet
  * result of request is about 3 new candidates: Ted, Mathias, Michael
   * Ted needs ABC'd ... probably a process of one more month
   * Mathias .. needs move into the team, to be proposed to become SA and also ABC'd before nomination can start
   * Michael .. works since longer time in the Software-Assessment-project team, is Support t/l and is ABC'd. So only needs nomination. Skills exists with the git repository. A plan is needed to move the Support t/l role on a replacement. Expected time: till end of this year
 * Documentation [[Software/Assessment/Documentation|Software Assessment Documentation]]
  * Discussed as part within "Software-Assessors current situation" topic
  * has to be completed with full command line instructions (w/o passwords), so a new SA can walk thru all instruction steps to fulfill the SA tasks
  * there are several git commands and procedures possible, to finish a task, so these instructions should reflect at least one solution with commands that an SA can walk thru. If a SA has more experiences with the git repository, he can feel free to add alternate procedures. But until there is no other procedural step known, each step has to be documented.
 * Testserver Current State
  * Current Patch on Testserver: [[https://bugs.cacert.org/view.php?id=876|Bug# 876]] needs review by a 2nd SA
  * "Thawte" patch [[https://bugs.cacert.org/view.php?id=827|Bug# 827]] has been added today by Markus onto cacert-devel, testserver
  * Uli wrote documentation, notified Testgroup
 * Signer deployment - Updates ?
  * Markus: step: named pipe / serial connection has been solved, next step: deploy the test CA
  * Uli: info from Wytze/Andreas: signer/comm module needs to be copied by a Critical Admin to get the current code
 * Automated testing system
  * Martin: installed Selenium client, started first tests to auto create a new account, test is ongoing
  * Markus: some infos about Selenium runtime and export functions
 * Next meeting: Tuesday, Oct 26, 2010

----
Action items:
 * Uli: propose from Software-Assessment-project team + Software-Assessor Markus: Michael to become new SA

----
 . CategorySoftwareAssessment