2018-07-25 Engineering Meeting


#1

Date/Time: 2018-07-25 @ 14:00 UTC / 10:00 EDT / 22:00 HKT
Click here to convert to your time zone
Length: 30 minutes
Meeting link: https://zoom.us/j/966890423

This meeting is for the engineering team, app developers and the community to discuss engineering concerns or questions.

Agenda

Please reply to this forum post with items you would like included on the agenda.

Each item should include:

Item name
Background information: Links to github issues, forum posts, etc with background information on the item
Desired outcome: what decision or deliverable would you like from the discussion of this topic at the meeting?


#2

Developer Issue Tracking

Background: We have a lot of ways that developers can submit issues and pain points in our repos, this forum, our slack, the weekly meeting etc. We want to do a better job integrating this information, so that we know what to prioritize and when. And finally, we’re trying to address 3 issues per cycle, so we want to have a public place to announce those.

Desired Outcome: I want to make sure that we have a good plan for logging issues as they come in, but more importantly, I think we should decide on a venue for public information about which issues we are working on in a given sprint cycle (we’re going to try to address 3 per cycle).


#3

Attendees

  • Larry
  • Will
  • Nico
  • Ken
  • Shreyas
  • Ryan
  • Tnl
  • Hank
  • Aaron
  • Jeff
  • Mary
  • Muneeb

Agenda Notes

Developer Issue Tracking

Background: We have a lot of ways that developers can submit issues and pain points in our repos, this forum, our slack, the weekly meeting etc. We want to do a better job integrating this information, so that we know what to prioritize and when. And finally, we’re trying to address 3 issues per cycle, so we want to have a public place to announce those.

Desired Outcome: I want to make sure that we have a good plan for logging issues as they come in, but more importantly, I think we should decide on a venue for public information about which issues we are working on in a given sprint cycle (we’re going to try to address 3 per cycle).

Possible Plan:

  • Different functional groups will do proposed issues for each
  • Post issues to the public engineering meeting thread
  • Community changelog (automated change log generator?)

Outcome: Aaron will make a plan.

You can also just add an automated changelog generator to each repo and put them in place. For collecting changes.

Test coverage vs shipping fast

Background: Do we want to consistently enforce test coverage requirements on pull requests?

Outcome: Yes!