Difference between revisions of "Tech Committee Agenda 22 May 2013"

From PKP Wiki
Jump to: navigation, search
(2nd draft)
(A bit reshuffling.)
 
Line 5: Line 5:
 
## Any particular needs that the group can help with?
 
## Any particular needs that the group can help with?
 
# '''At-large membership''': discuss poll results; identify top choices; make a plan for inviting nominees.
 
# '''At-large membership''': discuss poll results; identify top choices; make a plan for inviting nominees.
# 3 volunteers from '''members committee''' - status?
+
# '''3 volunteers from members committee''' - status?
# '''Reviewing our mandate''', cont'd:
+
# '''Reviewing our [http://pkp.sfu.ca/wiki/index.php?title=Technical_Committee#Mandate mandate], cont'd.'''  
## '''Charge #1''': Guide priorities and methodologies  
+
## Charge #1: provide technical input and advice on PKP’s software development methodologies and priorities. Last time the group came to the consensus that PKP priorities and methodologies are unclear. We are working towards fixing this so that we can begin to give input.
### Last time the group came to the consensus that priorities and methodologies are unclear to us, so we are working towards fixing this.
+
## James - overview of what priorities/methodologies documentation is available. How does the new WP site fit in and what's the status?
### New priorities-related document (thanks Alec et al): [http://pkp.sfu.ca/wiki/index.php/General_Software_Milestones Software Milestones page] needs review.  
+
## New priorities-related document (thanks Alec et al): [http://pkp.sfu.ca/wiki/index.php/General_Software_Milestones Software Milestones page] needs review.  
### Any other new documents we should be aware of?
+
## Overall need for better documentation and organization/accessibility of information. Need for improving developer relations. How?
### Perhaps each of us can commit to editing/clarifying a portion of the PKP documentation that we've used in our work?
+
## Discuss which format to use (blog? wiki?) for organizing/storing documents (e.g. agendas, meeting minutes, documentation). [https://groups.google.com/forum/#!topic/pkp-technical-committee/FcByQ7ESK7M See this Google group thread]
### Overall need for better documentation and organization/accessibility of information. Need for improving developer relations. How?
+
### James - update on new WP site?
+
### See [https://groups.google.com/forum/#!topic/pkp-technical-committee/FcByQ7ESK7M Google group thread] on which format to use (blog? wiki?) for organizing/storing documents (e.g. agendas, meeting minutes, documentation).
+
 
# '''Committee communication'''
 
# '''Committee communication'''
 
## [https://groups.google.com/forum/#!forum/pkp-technical-committee Google group]
 
## [https://groups.google.com/forum/#!forum/pkp-technical-committee Google group]
 
## IRC? There is a #pkp channel on chat.freenode.net
 
## IRC? There is a #pkp channel on chat.freenode.net
# Next meeting: how about Tuesday 18 June, 9am?
+
# '''Next meeting''': how about Tuesday 18 June, 9am?
 
# Anything else?
 
# Anything else?

Latest revision as of 14:48, 16 May 2013

Agenda

  1. New member introductions: Allan Bell (UBC), Bronwen Sprout (UBC)
  2. Quick round of updates
    1. What have we all been working on PKP-wise?
    2. Any particular needs that the group can help with?
  3. At-large membership: discuss poll results; identify top choices; make a plan for inviting nominees.
  4. 3 volunteers from members committee - status?
  5. Reviewing our mandate, cont'd.
    1. Charge #1: provide technical input and advice on PKP’s software development methodologies and priorities. Last time the group came to the consensus that PKP priorities and methodologies are unclear. We are working towards fixing this so that we can begin to give input.
    2. James - overview of what priorities/methodologies documentation is available. How does the new WP site fit in and what's the status?
    3. New priorities-related document (thanks Alec et al): Software Milestones page needs review.
    4. Overall need for better documentation and organization/accessibility of information. Need for improving developer relations. How?
    5. Discuss which format to use (blog? wiki?) for organizing/storing documents (e.g. agendas, meeting minutes, documentation). See this Google group thread
  6. Committee communication
    1. Google group
    2. IRC? There is a #pkp channel on chat.freenode.net
  7. Next meeting: how about Tuesday 18 June, 9am?
  8. Anything else?