14:00:02 <bh526r> #startmeeting Weekly Technical Discussion
14:00:02 <collabot`> Meeting started Thu Dec 20 14:00:02 2018 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:02 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:02 <collabot`> The meeting name has been set to 'weekly_technical_discussion'
14:00:30 <bh526r> #topic Roll Call
14:00:49 <bh526r> #info Bin Hu
14:00:57 <bh526r> #info Trevor Cooper
14:01:52 <bh526r> #info Mark Beierl
14:02:49 <bh526r> #info Cristina Pauna
14:04:58 <bh526r> #info Pierre Lynch
14:05:04 <bh526r> #info Al Morton
14:05:30 <bh526r> #topic Discussion of Code and Release Quality
14:06:52 <bh526r> #info Cristina introduced the process of implementation
14:07:09 <bh526r> #info There are 6 steps in the process
14:07:43 <bh526r> #info Step 1 is to create standard format for input
14:08:10 <bh526r> #info Step 2 is to gather proposals
14:08:53 <bh526r> #info Step 3 is to debate proposals, polish them and get them in a better shape. This can be done in weekly technical discussion
14:09:09 <bh526r> #info Step 4  is to get approval from TSC
14:09:30 <bh526r> #info Step 5 is to create a JIRA for each proposal
14:10:04 <bh526r> #info Step 6 is to monitor progress, e.g. get them implemented, etc.
14:11:08 <bh526r> #info Mark asked if we want to achieve a consistent format of all projects, or we allow each project flexibility
14:14:41 <bh526r> #info Cristina explained we intend to help project, if one proposal gets buy-in of all projects, they will adopt it. If one proposal only gets support of very few projects, or no resources, then it won't be adopted.
14:15:13 <bh526r> #info Mark likes the approach of project helps each other
14:15:26 <bh526r> #info Cristina further introduces the template
14:16:10 <bh526r> #info as the Step 1
14:18:57 <bh526r> #info The template includes (1) Problem description (2) Possible solution and Pros and Cons analysis (3) Resources needed such as HWs and human resources (4) Proposed Changes and (5) Owner of Implementation
14:20:39 <bh526r> #info Cristina gives an example of using template to describe (1) Use FuncTest to Verify Installer Patches (2) Reduce the time it takes for running tests
14:23:49 <bh526r> #info Georg Kunz
14:26:55 <bh526r> #info Al says it is worth trying
14:27:13 <bh526r> #info Trevor asks if there is specific area for each project
14:27:43 <bh526r> #info Cristina doesn't think there is a reason to have a limit
14:28:33 <bh526r> #info Trevor thinks TSC may make some suggestions
14:29:40 <bh526r> #info Mark thinks the idea is that anyone can make a proposal, and if enough interest, TSC may make guidance of where resources should go
14:30:40 <bh526r> #info Trevors thinks eventually we need to apply the process to direct the direction
14:31:03 <bh526r> #info Cristina thinks the area is the code and release
14:33:15 <bh526r> #info Mark thinks there is a TSC checkpoint in the process. When TSC takes the checkpoint, TSC will consider the strategic direction.
14:33:52 <bh526r> #info Mark suggests that we add a bullet point of TSC checkpoint to check alignment with strategic direction
14:34:07 <bh526r> #info Trevor likes this suggestion
14:35:04 <bh526r> #info Mark thinks TSC's role is to help proposal get more alignment with strategic direction
14:35:56 <bh526r> #info TSC needs to take into account the strategic direction to make go/no go decision
14:36:24 <bh526r> #info Cristina will add a note in the template for TSC to consider aligning with strategic direction
14:38:23 <bh526r> #info Mark is happy with it
14:41:48 <bh526r> #info Cristina will share the proposal and etherpad in the mailing list after new year. Input and comments are expected from community discussion in mailing list, and make proposal more polished and mature.
14:42:28 <bh526r> #info The target is to discuss it again on Jan 24.
14:42:37 <bh526r> #topic AOB
14:42:44 <bh526r> #info Meeting adjourned
14:43:05 <bh526r> #endmeeting