SRP Telecons. DanaBalser reported that the telecons went well but there were some issues in finalizing the reviews. One chair had difficulties getting the panel to complete the reviews on time and had to craft two instead; and another chair had difficulty converging with a few members on a few proposals. MarkClaussen reported that one panel was quite slow but they did finish on time. AmyMioduszewski reported that one panel was bogged down on Triggered proposals and whether to approve a proposal even if it were unlikely to get time; we should discuss this at the TAC f2f meeting before the Triggered proposal discussion to make sure all Triggered proposals are treated the same. One panel was quite efficient and they had entered the consensus comments before the telecon. LewisBall suggested we discuss this at the TAC f2f meeting postmortem; that is, get feedback from the chairs about their procedures and experiences during their telecons. AmyMioduszewski suggested that we add one bullet point to our SRP telecon introduction to emphasize that what matters to the outcome of the telecon is the linear-rank.
Large Proposal Telecon. DanaBalser reported that the Large Proposal Telecon will be held 12 April 2019 (10:00-12:00 EDT or 08:10:00 MDT). He will make sure rooms are reserved.
Face-to-Face Meeting. DanaBalser will ask ToneyMinter about the reception and the GBT tour. There will be 8 TAC members and 7 observatory people traveling to GB for the meeting. There will be one remote TAC member and several remote observatory staff. DanaBalser will check about using zoom for the remote TAC member.
PHT. RickLively reported that he has investigated the Any configuration ticket and has in principle converged with AmyMioduszewski on what needs to be done. There are some technical issues connecting the configurations to the semesters (which is inside the PST). AmyMioduszewski noted that it might be useful to limit the number of semesters to 2, otherwise it will be hard to automatically assign the Any configuration to a specific semester. We agreed that since most Any configuration proposals only ask for 2 semesters this is really not a big problem; we just handle these few manually. We briefly discussed the metrics ticket. RickLively was not sure of the status but felt that it was not a priority. LewisBall will bring this up at the next planning meeting (DanaBalser will send him info).
Gender-based Proposal Success. AnandCrossley summarized a simplified analysis of gender-based proposal success (similar to HST). We briefly discussed these results.