Changes between Version 1 and Version 2 of org/meetings/2017Montreal/Notes/InterTeamComms


Ignore:
Timestamp:
Oct 30, 2017, 11:57:12 PM (2 years ago)
Author:
dcf
Comment:

Fix syntax.

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2017Montreal/Notes/InterTeamComms

    v1 v2  
    11Things we should do:
    22* Nick: roadmaps tend to be self-contained to the specific team. we should
    3 integrate "who else is involved and what other teams are affected" into the
    4 roadmapping.
     3  integrate "who else is involved and what other teams are affected" into the
     4  roadmapping.
    55* Julius: let's have a meeting to only discuss interdependencies (i.e. how
    6 the vegas team meeting is supposed to run, rather than how it is supposed
    7 to run now). Let's keep it short and focused on that though.
     6  the vegas team meeting is supposed to run, rather than how it is supposed
     7  to run now). Let's keep it short and focused on that though.
    88* Isa: consider leveraging ticket keywords on trac to organize things
    9 "horizontally" across teams and etc. on top of bucketing things into
    10 components.
     9  "horizontally" across teams and etc. on top of bucketing things into
     10  components.
    1111* Julius: very very low noise channel that pushes important updates to all
    12 of tor.
     12  of tor.
    1313* Mark: advertise the UX team's ticket triage and ux team meeting model.
    1414
    1515Conversation highlights:
    1616* Nick: doesn't think he's neglecting people, but other teams feel
    17 neglected.
     17  neglected.
    1818* Mark: We should handle dependencies between teams better. The browser
    19 team does not know how to handle all the dependencies.
     19  team does not know how to handle all the dependencies.
    2020* Damian: Doesn't have any communications because he's not explicitly on a
    21 team. I want a tor-weekly news like thing. Vegas leads summaries are not
    22 summaries of what the teams have done, but what that specific person has
    23 done.
     21  team. I want a tor-weekly news like thing. Vegas leads summaries are not
     22  summaries of what the teams have done, but what that specific person has
     23  done.
    2424* Isa: we're trying to build a newsletter, and each team does do the
    25 monthly summaries. Not saying it's going to solve everything, but it is
    26 happening and should help somewhat.
     25  monthly summaries. Not saying it's going to solve everything, but it is
     26  happening and should help somewhat.
    2727* Linda: vegas summaries, monthly summaries, and etc. are all good for
    28 summarizing what has happened, but I have trouble coordinating for the
    29 future--I wish I knew the different teams' roadmaps so that I can plan
    30 accordingly.
     28  summarizing what has happened, but I have trouble coordinating for the
     29  future--I wish I knew the different teams' roadmaps so that I can plan
     30  accordingly.
    3131