preshow

vimb !!! noffle wrote about it
i3, tiling window managers
pull requests
prios

from the orga thread

• your thoughts on introducing some new users - cryptix
• old feature request bump onto %ssb-graphviz
• using yarn to install node_modules over ssb
• running ssb full client in the browser (!!!) - dominic
• has anyone tested the flume branch of sbot? - dominic
• porting the ferment self-description on profiles to patchbay
• general edits or introducing a mark as deleted thing to give authors the option to hide mistake msgs
• As the project becomes more popular/more people get involved, what are the current development priorities for Bay?
• Are there any pull requests that can be cleared from the 'bottleneck' mentioned 2 weeks ago -- by saying 'no' to them flat out?
• reporting back on the new modular css

note: [x] means let's do these in a quick status/feeback style, rest for later

checkin

• cryptix: survived 33c3 and nye. ohai 2017
• dominic: back in new zealand
• ev: tried yarn (alt-npm)
• gb: #engineeryear
• matt: not much ssb lately, nye gig (recording?), maybe more ferment soon
• mix: certain event preperation ;)

agenda

quick status/feedback first

• talebay (250 keys) - are we ok with flooding the onto here. GO FOR IT
• sbot in the browser: looks viable, maybe refitting ssb-query -links2 maybe
• flume pr: %JBJRvTo...
• go for about/description into patchbay
• modular css: about_refactor is on master, try it out! easy overwriting wanted (themes basically)

actions

• dominic : will be watching for flume feedback
• mix : have a go at adding a theming css file
• ev : if bored will have a look over ssbc repos / issues

discussing git-ssb vs github

pull request review to hard in git-ssb-web right now
Mix uses : pull-requests in github for easy review features, and treats git-ssb as master

modularising code (re)view stuff from git-ssb so we can look it in patchbay

conversation about *bay modules

'essential' / 'core' modules
folders vs prefixes?

pr bottlenecks

stale pull-requests, status tags like (wip)

dev priorities

dominic:

• encrypted group messages
• gossip refactor

mix:

• modular modules :P
• longer term - git-bay / patch-git
• more storytelling
  • practicing different stories
  • writing down stories (so shareable)

gb:

• world domination

cryptix:

• some meta stuff like (about descrion, external confirm)

matt:

• ferment: dead blobs(/torrents)
  • cryptix collaboration