Ok, let's go for Monday, 10/22:
2pm-3pm PDT
US 866-545-5223
Intl 865-673-9887
AC 5540840
Proposed Agenda
* Review/revise order-of-work priority assumptions
- Some assumptions
- We want to move the gates outside to enable full open development
by all community members
- We can technically move a gate outside before full open
development is possible (sponsors continue to file RTIs, for
example).
- Need list of GK tools in priority order (is this the right order?)
- Required by SFW
- to transition the SFW gate to hg
- to move the SFW gate outside
- for external committers to work on the outside SFW gate
- Required by ON
- to transition the ON gate to hg
- to move the ON gate outside
- for external committers to work on the outside ON gate
* Review the list of gk tools on genunix.org
- http://www.genunix.org/wiki/index.php/gateTools
- Make sure it's complete
Answer MikeK's question: do we track gate hooks as part of
this list or separately? Regardless of where we track,
make sure we have the complete list of gate hooks.
- Note which, if any, are 'done'
- Confirm which tools are required for each of the priorities
agreed to above
- Note any owners of tools on the list
* Create a plan for creating a dummy gate to use for testing
* Discussion of gate hooks
They need access to:
- CR number and synopses (for synopses checks).
- CR number and RTI approved state (for RTI checks).
I think Danek had mentioned that he'd like the synopsis crosschecked
against the RTI too, but I'm still not entirely sure how that's not a
problem for WebRTI rather than the gate.
* Discussion of documentation as it relates to the GK tools
Best practices (should I create branch in workspace or rather create
new clone; and why ?). What to do if Mercurial screws repository
(happens to me ~ once a week). Differences between Mercurial and
wx/TeamWare.
* What else?
