Status Devs Meeting 12, Agenda

[oskarth]

Meeting Date/Time: Monday 2019-02-11 at 13:00 UTC
Meeting Duration 1.5 hours
YouTube Live Stream Link https://www.youtube.com/c/Statusim/live
Livepeer Live Stream Link TBD

For each agenda item, please provide context (things non-initiated people need to know, links etc) and goal (desired outcome of discussion) for agenda items.

Please comment below with things you want to discuss, together with context and desired outcome.

[oskarth]

One feedback that's worth re-iterating. These meetings should probably focus on matters that:

• are technical in nature
• would benefit from sync conversations
• can be decided upon during the meeting, i.e. doesn't require a lot of async research etc

Do people generally agree with this or are there other viewpoints?

[oskarth]

1. Better PRs
   a) how can we avoid long PRs? the use of feature flags
   b) acceptance criteria and design review

2. Protocol discussion and Q&A
   Some time to ask questions and discuss protocol workshop etc

[rachelhamlin]

There was a suggestion by Eric on the chat sync to discuss push notification navigation.

With both deleted chats and old PNs from blocked users (PR just merged), the PNs open into an Unknown chat. Not sure if this is affected by Pedro's recent work to improve PN navigation.

[0xc1c4da]

Is it worth discussing https://discuss.status.im/t/musings-on-key-management-aka-whisper-decoupling/1034 would love feedback and any issues I may have missed, it probably requires async research, but everyone should be aware of the potential changes

Status.im

Musings on Key Management (aka 'Whisper Decoupling')

Finally had a few hours this Sunday to think about the Key Management stuff. Background We strive to be a private means of communicating, whether that is via text, media or transactions. However currently, it is easy to see a user’s entire transaction history (public blockchain’s yo) based on whisper identity. To improve this there is a desire to generate new keypairs for both on-chain transactions and communication. Previous discussions have been thoughtful & fruitful, but have had some issue...

[oskarth]

https://notes.status.im/ZXI1PLCLSeiuDTwAweRLxQ#

Core Dev call 12 - CodiMD

[oskarth]

Follow up to PR discussion https://discuss.status.im/t/better-pull-requests-process/1044/2

Status.im

Better pull requests process

Problem We have too big PRs and they are merged too slowly. This leads to general frustration, regressions, harder to revert commits, additional workload to rebase, a longer feedback cycle, etc. Context We discussed this during the last Core dev call. See below for notes. This is mostly relevant to Status Core and related swarms, though expertise from other projects that have a solid workflow is much appreciated (cc @iurimatias e.g.). Additionally, we are practicing trunk-based development htt...

[oskarth]

#17